Third Party Developer Blog

Greetings space developers, Just wanted to send out a short update to notify everyone of a behavioral change in ESI. By the time you're reading this, ESI will have stopped sending optional boolean attributes when they are not True. If a spec has the boolean as required, the value will always be sent. Otherwise the key/value will only be sent if the value is True. An object property is required only if it is listed in the object schema's required array. For example, the alliance object in the GET /v1/corporations/{corporation_id}/alliancehistory/ 200 response array, each object has an alliance property, which is defined as: { "description": "alliance object", "properties": { "alliance_id": { ... 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. Here on this blog we regularly mention the fact that ESI uses a framework called Swagger. In fact, the word "Swagger" is directly in the name (EVE Swagger Interface)! We also regularly mention that Swagger provides the capability of auto generating code for the programming language of your choice. However, it's not entirely obvious from looking at Swagger documentation how one should go about generating and using a client library. This blog will cover two ways to generate a library using ESI with tools provided ... read more