Login
Login

Dev Insights Blog

Updates, tips, and stories to keep you in the loop

By: The ESI Development Team

Published: 2026-02-24

Spring Cleaning: legacy routes removed 24 March 2026

Hi all,

Time to retire some old parts of the ESI infrastructure. On 24 March 2026, a batch of legacy routes will be removed. For anyone still using them, consider this the final heads-up to switch before they're gone.

/verify

The /verify endpoint accepts a JWT and returns details about the token. In most cases there's no need to call ESI for that as JWTs can be decoded and validated offline. The token already contains the information; no round-trip required.

When verification via an API is needed, https://login.eveonline.com/v2/oauth/verify is effectively a drop-in replacement. From 24 March onward, /verify will redirect there. The redirect will be removed one month later, on 28 April, so pointing the client at the OAuth URL or validating offline are the best options.

/status.json

The old status route only showed a partial list of routes and their health and ran on older infrastructure. It was superseded by /meta/status back in November — see A better view on status: improving ESI health monitoring for the details. The new endpoint has clearer status values (OK, Degraded, Down, Recovering) and covers all routes.

Applications still using /status.json should migrate to /meta/status before 24 March.

/diff, /versions, /headers

With the new API versioning in place, /diff and /versions no longer have a purpose. /headers has been deprecated for a while and sees very little use.

Swagger specs: /swagger.json and friends

The old /swagger.json spec (the legacy "meta" spec) is outdated and will be removed. Some traffic still hits it, but clients using generic User-Agents like python-requests or python-urllib can't be identified — so anyone in that boat should move to the OpenAPI specs.

Also being removed on the same date:

  • /dev/swagger.json and /_dev/swagger.json

  • /legacy/swagger.json and /_legacy/swagger.json

/latest/swagger.json is staying for a bit longer to give older applications more time to upgrade. Reminder: it is no longer updated. New routes and changes only appear in the OpenAPI specs. Applications still using /latest/swagger.json should move to OpenAPI soon.

Summary: what goes away 24 March

  • /status.json

  • /diff/*

  • /versions/

  • /headers/

  • /swagger.json

  • /dev/swagger.json and /_dev/swagger.json

  • /legacy/swagger.json and /_legacy/swagger.json

/verify will start redirecting to https://login.eveonline.com/v2/oauth/verify (redirect removed 28 April).

If any of this affects your application and you need help migrating, the EVE Discord channel #3rd-party-dev-and-esi is the place to ask.

Cheers,

Your friendly developers of the EVE Sunset Initiative (working title)