The SDE over HTTP: static data, dynamically
Static capsuleers,
The Static Data Export (SDE) has a new home: sde.evetech.net. There will be no zip to download and nothing to unpack: you ask for a single record, a whole table, or everything at once, using plain HTTP requests.
The zip files stay around for now, so there's no rush. Have a look, and start moving over when you're ready. If you use the /universe routes on ESI, read on: those related to static data are going away with today's compatibility date (2026-11-19).
Why a new way?
Until now, getting static data meant downloading the zip, unpacking it, and converting it into whatever your application needs. That's fine if you want everything. It's a lot of work if all you want is the name of one ship, the details of that one solar system, or what a handful of blueprints need.
There was another problem: more than a few applications scan the /universe routes on ESI after every downtime to see what changed. All those requests land on Tranquility, which isn't great for performance. To make things worse, /universe and the SDE didn't always agree on the shape of the data, so new fields often showed up in one but not the other.
Meet the SDE API
The SDE API is made to be explored. Every response links to the next level, so you can click your way down from the root:
sde.evetech.net lists the tenants.
sde.evetech.net/tranquility/ lists the releases, newest first.
sde.evetech.net/tranquility/latest/ shows the current release: its build number, its release date, and every table with its links.
For a single record, use <key>.json. Say hello to the Rifter at sde.evetech.net/tranquility/latest/types/587.json.
For a whole table, pick your format:
types.jsonl: the table in JSON Lines, one record per line, withtypes.schema.jsondescribing a single record.types.fbandtypes.fbs: the table in FlatBuffers, with its schema.
FlatBuffers is the new kid on the block: a binary format that is very fast to read, especially when you only need a few fields from each record. In fact, the SDE API itself runs on these files.
And yes, that's a schema for every table, in both JSON Schema and FlatBuffers. You've been asking for this for a long time, and it's finally here! There are no descriptions yet, but that is being worked on.
Two small things to keep in mind:
Files are always sent gzip-compressed. Most HTTP libraries handle this for you; with
curl, add--compressed.There's no YAML; the SDE API only serves JSON Lines and FlatBuffers.
Getting everything at once
Miss having the full SDE on disk in JSONL, like the zip gave you? That's a one-liner on Linux:
curl -sL --compressed https://sde.evetech.net/tranquility/latest/ \ | jq -r '.tables[].jsonl.url' \ | xargs -n1 -P8 curl -sSLO --compressed
And don't worry about a new release landing halfway through your download. The URLs from latest/ point to that exact release, so your files always belong together.
Staying up to date
We publish a new release whenever the data changes. After a Tranquility deployment, it shows up in about 10 minutes, the same as for the zip files. Releases on the SDE API happen a bit more often, though, for example when new military campaign objectives start. This has one side effect: build numbers are no longer unique. Several releases can share the same build number, so use the release field to tell them apart.
/tranquility/latest/ always redirects to the current release. Every release also has its own URL, like /tranquility/20261116T124006Z/. That's handy when you want a batch of requests to all come from the same release. Don't hold on to it for long, though: we only keep the current and the previous release around. Older release URLs stop working once their releases are no longer retained.
You also don't have to download everything every time:
Each table has a
versionfield that only changes when the data in that table changes. Map data, for example, is the biggest part of the SDE, but it rarely changes, so most of the time you can skip it.You can also let HTTP do the work. Keep the
ETagheader from your last download, and send it back in theIf-None-Matchheader next time. If nothing changed, you get a304 Not Modifiedand you're done.Every release comes with two extra tables:
_changeslists what changed since the previous release, and_schemaChangeloglists the changes to the schemas.
The SDE API doesn't go through Tranquility, so the daily downtime doesn't touch it. Everything is served from a CDN, and most requests are answered from cache.
Moving over
The zip and /universe
The zip files at developers.eveonline.com/static-data stay available for now. Over time, we'd like to retire them too, so we recommend moving to the SDE API. If you do something with the zip that the SDE API can't do, let us know!
Most /universe routes on ESI serve static data, and the SDE API is now the better place for that. So from the compatibility date 2026-11-19, these routes are no longer available via ESI. There are a few exceptions: routes under /universe that do not serve static data will be kept around:
/universe/ids/universe/names/universe/structures/universe/system_jumps/universe/system_kills
Changes to the JSONL
The data is the same as in the zip, but the shape is a little different. Here's what to look out for:
No more
_keyand_value. Keys now have a proper name, like typeID, and always come first in a record. The JSON Schema tells you which field is the key.Named fields in
missionsandfreelanceJobSchemas. Mission messages changed from{"_key": ..., "en": ...}to{"kind": ..., "text": {"en": ...}}. In the same way,freelanceJobSchemasuses named fields instead of_keyand_value.Plain JSON numbers. JSON doesn't see a difference between 1 and 1.0, so a mass of 1.0 is now written as 1. Very large values, like massDust on moons, are still written as floats, so JavaScript and other languages can read them safely.
Required fields are always there, even when they're empty. For example, typeLists now always has all six lists, where the zip left out the empty ones. Optional fields are still left out when they have no value.
Wrapping up
With the SDE API, you fetch only the static data you need, whenever you need it. Whether it's a server-side application or a browser: we hope this makes it easier and faster to work with EVE's static data.
As always, we love to hear your feedback. Join us on the official EVE Online Discord, channel #3rd-party-dev-and-esi-chat, to talk about this and other ESI improvements.
Cheers,
Your friendly developers of the EVE Static Information (working title)