YURIX

Eve ESI Quirks

Spring 2025

Use the creator code RECURSIVETREE during checkout on the eve store to support me with up to 5% of your purchase :)

If you are new to EVE Online third party tool development and excited to get started with using ESI, I must unfortunately disappoint you. ESI is in on fire. CCP doesn't invest nearly as much time into maintaining and documenting ESI as it is required for smooth operations. You can count yourself lucky if they fix an endpoint after it goes down, but fixing old bugs or updating the documentation just doesn't happen. At least, this has been the case in the past years (I'm writing this in November 2024). With this post, I aim to share some undocumented behaviours and tricks that could be useful for others.

/markets/{region_id}/orders/

For citadels, this endpoint returns buy orders with a larger range than just the citadel itself. Sell orders and buy orders within a citadel are not returned. To get a complete picture of the market in a region, combine this endpoint with scrapes of citadel markets using the citadel market endpoint.

/markets/{region_id}/history/

There are invisible, undocumented rate limits on this endpoint. If you exceed them, you can get banned. A safe value is around 100 requests per minute.

Also, please don't even ask why they have undocumented rate limits...

Structure Names

To get the name of a citadel from a location_id, for example from the assets endpoint, you can use the /universe/structures/{structure_id}/ endpoint. However, when you can't docke there, this endpoint doesn't work and there is no other way to get the name of the structure.

SSO

Apparently, requesting ALL scopes can trigger an error 400 - Request too long. The only fix is to remove a few scopes.

The same can happen if you select "remember me" on too many accounts.