This thread will be used going forward for updates and releases for EveKit. Things are still somewhat fluid in the ESI. You can expect regular updates as we incorporate new/modified ESI endpoints into EveKit. The next upcoming change is documented below.
ESI 2018.04.30 UPDATE on 2018.05.05 at 0000 UTC (midnight 2018.05.04)
We’ll be updating EveKit from the ESI as it stood on 2018.04.09 to the ESI as it now stands on 2018.04.30. EveKit uses the ESI Java client released here which is distributed via Maven releases tagged by date. So in this particular case, we’re moving to the 1.0.0.20180430 release of the enterprises.orbital.eve.esi.client package.
This update has a number of important changes. Please see the release notes below.
RELEASE NOTES
-
The chat channel endpoints have been moved to legacy. As of this release, we will no longer synchronize against these endpoints. Also, the corresponding ESI scope will be removed from any accounts that had it. We will retain any data we already synchronized and make it available in its current form until (or if) new chat channel endpoints are released.
-
Contact labels for corporations are now supported for the ESI. We have enabled this support in EveKit. As of this release, if your scope allowed access to corporation contacts, we’ll now start synchronizing and storing contact labels as well.
-
The wallet journal endpoints received a few new fields while eliminating a few others. The new fields are context_id, context_id_type and description. These fields replace (to a degree) first_party_type, second_party_type and all the “extra info” fields. It turns out there are logical mappings to context_id for most of the fields in “extra info” except for npc_id and npc_name. To preserve as much data as possible, we are therefore populating historic description fields with the string “first=<first_party_type> second=<second_party_type> npc_id=<npc_id> npc_name=<npc_name>”. Many of these values will be NULL. The remaining fields will be copied to context_id (with a corresponding setting in context_id_type) according to the table below.
| If this “extra info” field is set… |
then it will be copied to context_id and context_id_type will be set to this value… |
| alliance_id |
“alliance_id” |
| character_id |
“character_id” |
| contract_id |
“contract_id” |
| corporation_id |
“corporation_id” |
| destroyed_ship_type_id |
“type_id” |
| job_id |
“industry_job_id” |
| location_id |
“structure_id” |
| planet_id |
“planet_id” |
| system_id |
“system_id” |
| transaction_id |
“market_transaction_id” |
1 Like
UPDATE: this release will be delayed until 0000 UTC on 2018.05.08 (midnight 2018.05.07) to allow more time for downstream users (e.g. jEveAssets) to prepare for the change.
1 Like
This maintenance is now complete. In addition to the changes described above, we have also released support for several new endpoints:
-
Character ship fittings are now retained. This change requires adding the “fittings” mask to your EveKit access key. As a reminder, you can change your access key mask using the “modify” option in the EveKit Data Access Key view.
-
Character loyalty points are now retained. This data is accessed under the “character sheet” mask of your EveKit access key.
-
Character mining ledgers are now retained. This change requires adding the “mining ledger” mask to your EveKit access key.
-
Corporation mining extractions, observers and observations are now retained. This change requires adding the “mining ledger” mask to your EveKit access key.
1 Like
EveKit 4.2.1 updates were pushed today adding several new synchronization models. Specifically:
-
If your character’s corporation is in an alliance and your account has the esi-alliances.read_contacts.v1 scope, then EveKit will now synchronize your alliance contacts along with any character contacts. This data is included under the ‘Contact List Access’ permission in your EveKit access key.
-
Character opportunities are now synchronized if your account has the esi-characters.read_opportunities.v1 scope. Unfortunately, there is an ESI bug which is preventing the download of opportunities at the moment. This feature will be disabled until the ESI bug is fixed. This data is available via EveKit access key using the Character Sheet Access permission.
-
Character fleets are now synchronized if your account has the esi-fleets.read_fleet.v1 scope. This data is available via a new EveKit access key permission called Character Fleets Access. You’ll need to add that permission as needed to any existing keys.
-
Corporation structures are now synchronized if your account has the esi-corporations.read_structures.v1 scope. This data is available via a new EveKit access key permission called Structure List Access. You’ll need to add that permission as needed to any existing keys.
New REST API endpoints have been added for the new model types. Also, nightly snapshots will start including the new models starting tomorrow.
1 Like
EveKit has been updated to the latest ESI in order to pick up the new “is blueprint copy” flag on assets. EveKit is using version 1.0.0.20180601 of this client, which can normally be found on Maven Central. The new asset attribute will be populated the next time EveKit synchronizes your assets.
As usual, the EveKit REST API endpoints have been updated to allow selection against the new asset attribute. Also, nightly snapshots will start including the new asset data starting tomorrow.
1 Like
EveKit Maintenance 0100 UTC 2018-06-16
EveKit will be updated to ESI 2018-06-11 on 2018-06-16. A post will be made when this maintenance is complete.
This update includes the following changes:
- New enumeration values for Character Notifications and Character Assets.
- Contacts (Character, Corporation and Alliance) now support a list of label IDs instead of a single label.
The latter change requires a small model update. The EveKit model for Contacts now stores an array of labels instead of a single value. The single label values that were present on historic data will be stored in an array of length one.
As usual, account snapshots will update automatically within 24 hours.
1 Like
This maintenance is now complete.
1 Like
EDIT: As of 0432 UTC the site is back up again and synchronizing data. Apologies again for the outage.
EveKit is currently having a disk issue. The site is down at the moment, but should be back up soon. No data has been lost. However, account data can’t be synched from ESI until the site is backup. Apologies for the outage.
1 Like
EveKit Maintenance 2100 UTC 2018-07-09
EveKit will be updated to ESI 2018-07-09 on 2018-07-09. A post will be made when this maintenance is complete.
This update includes the following changes:
- Pick up the change to Faction War Systems which converts the “contested” field from a boolean to an enumerated type.
- Add the new “issued_by” field to Corporation Market Orders.
Both changes will require model updates. The faction war systems change only affects reference data (i.e. not data synchronized to any player account). Going forward, the “contested” field will now be enumerated according to the latest ESI specification. For historic data, the value will be set to “contested” if the previous value was “true”, and “uncontested” otherwise.
Corporation market orders (which are synchronized to player accounts) will now include the “issued_by” field. For historic data, this field will be set to 0. Note that this field will also appear in character market orders (the model is shared between both types), and will also be set to 0.
As usual, account snapshots will update automatically within 24 hours.
1 Like
This maintenance is now complete.
1 Like
For those of you that use EveKit’s API for the SDE, I’ve just released 2018-08-27. More details on the blog post here: http://blog.orbital.enterprises/2018/08/sde-2018-08-27-released.html
2 Likes
EveKit’s API for the SDE has just been upgraded to the 2018-09-17 SDE release. More details on the blog post here: http://blog.orbital.enterprises/2018/09/sde-2018-09-17-released.html
1 Like
Today, we’ve released improved documentation for EveKit, including an explanation of the interface, as well as guidance for using the APIs in your own projects. We’ve also improved the documentation around the various 3rd party APIs we support (e.g. market data services).
You can view the documentation from the main site, or you can go directly to the new docs here (hosted at “readthedocs”).
1 Like
EveKit will be down/intermittent for a short maintenance window this evening from 2018-10-09 01:30 UTC to 2018-10-09 02:30 UTC. More information about the update can be found on the blog post.
1 Like
DB maintenance has completed. Model synchronization was disabled from 2018-10-09 01:30 UTC to 2018-10-09 02:00 UTC. All model data is now synchronizing as usual.
1 Like
EveKit’s API for the SDE has just been upgraded to the 2018-10-09 SDE release. More details on the blog post here.
1 Like
EveKit’s API for the SDE has just been upgraded to the 2018-11-13 SDE release. More details on the blog post here.
1 Like
EveKit’s API for the SDE has just been upgraded to the 2018-12-14 SDE release. More details on the blog post here
1 Like
EveKit has been updated today to support the new “war_eligible” flag in corporation sheets. This flag will be populated as “true” for historical data, and will populate from ESI for data going forward. The new field will show up in your next daily snapshot, and is accessible now from the the API. Since this change required an EveKit API addition (i.e. new field on corporation sheet), you may need to regenerate your EveKit client against the our Swagger definition file (https://evekit-model.orbital.enterprises/api/swagger.json).
1 Like
EveKit’s API for the SDE has just been upgraded to the 2019-01-17 SDE release. More details on the blog post here
1 Like