Third Party Developer Blog

Hi developer friends! We'd like to inform you of upcoming SSO changes which might affect your application if you are developing 3rd party apps using ESI or using the EVE SSO for user authentication. We'll be making the following changes on November 1st 2021. Deprecating obsolete endpoints The old OAuth endpoints oauth/authorize, oauth/token and oauth/verify will be deprecated. You should move your application over to v2/oauth/authorize and v2/oauth/token instead. The oauth/verify endpoint will also be deprecated, since the v2 endpoints return a JWT token, enabling your applications to validate the JWT tokens without having to make a request to the SSO for each token. Applications can fetch the required EVE SSO metadata from https://login.eveonline.com/.well-known/oauth-authorization-server to be able to validate JWT token signatures client-side. The deprecated endpoints might be removed at any given time ... read more

On 30 July 2020 in the ESI changelog we announced the deprecation of v4 version characters/{character_id}  ESI route on 15 September and subsequent removal on 21 September. Unfortunately we still see heavy traffic hitting that route which as of now has legacy status. Accordingly we've decided to postpone the (admittedly quite abrupt) removal. Its been rescheduled and now it will happen on 21st October 2021.  Please spread that information if you know any developer that might not follow changelog and/or Tweetfleet. 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. Deprecated Information The information presented on this page is depreciated. Please see https://docs.esi.evetech.net/docs/sso/ for up-to-date information. Last month, we talked about auto generating a client library for ESI using Swagger Codegen. This month we will expand on this by stepping through the SSO authentication flow and using that authentication to make a call to the ESI endpoint /characters/{character_id}/standings. Typically, one would set up a server to handle most of this process, but today we're ... 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. 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