Third Party Developer Blog

Hello developers CCP is making a number of changes to the developer agreement. The primary purpose of these changes is to allow for persons other than the original developer to enter into the agreement and get access to the resources for EVE Online made available by CCP. An example of such a user might be someone that has downloaded an application written by someone else. As the author of the application can't include a client ID and secret in the application (as they become public), the user will need to provide their own. Since the end user is not the original author of the application, they were not allowed to sign the agreement. The full updated Developer License Agreement can be found here. If you just want to see the changes, they're detailed below. Additions are in bold, removed text is marked with ... read more

This blog post is part of a series of blogs examining best practices for ESI development. Each blog will be published on the 8th of each month during the journey towards XML API and CREST’s termination date. The legacy APIs will be terminated on May 8th, 2018, or earlier if metrics signal a trivial level of usage. Moon mining is coming to EVE Online on October 24th in the Lifeblood expansion and, for the first time ever, new ESI endpoints will accompany this new feature's release! The new endpoints will be onlined a few hours after downtime on October 24th for Tranquility. We have already released revamped moon mining onto our test server, Singularity, along with the mining ledger ESI endpoints so that you can begin making software for this feature now. There are three new endpoints to accompany mining ledgers. ... read more

Greetings developer capsuleers, Team Tech Co. previously blogged about a set of range checks that we placed on /universe/names/ and /characters/affiliation/ that made these ESI endpoints return blanket 404s for the range of IDs encompassing Dust characters and legacy EVE characters and corporations. As of today, with the enabling of error limiting, we have now removed these range checks. This means that any 404s you get from /universe/names/ and /characters/affiliation/ will be legitimate 404s. Remember that given a set of IDs if any of those IDs are not valid you will get a 404 even if some of the other IDs in the set are valid. As always, you can come talk to us in the tweetfleet slack (use this link to join) in the #esi channel if you have further questions. -Team Tech Co. read more