Third Party Developer Blog

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. This blog explains best practices for autogenerating language specific clients from the ESI swagger spec. When generating code from one of the named routes (e.g. https://esi.evetech.net/latest/swagger.json), you may have noticed the resulting client library uses /latest as the version in all its URL calls. You can see why if you look at this fragment of the swagger spec from the above URL: { "basePath": "/latest", "host": "esi.evetech.net", "info": { "description": "An OpenAPI for ... read more

As outlined by the previous blog, we’re upgrading the image server to an entirely new service that better fits the modern developer environment and needs. This means a friendlier, RESTful API, dynamic resizing, multi-tenancy support, and all these will be served through a global CDN. A New Domain Initially, we thought about sharing the same domain as the previous image server, but the change is way too subtle. So we will use a completely new domain for the new image service: images.evetech.net Actually, the new service has already been deployed and running for a while, so go ahead and give it a try! It has some documentation with a very “minimalistic design” for now, which will likely be improved in the future. The New APIs    There are two main APIs in ... read more