API Documentation
This section of the site contains documentation for all APIs available on the site. You can select a method to view information for from the menu above.
This page contains general usage information, guidelines for use, recommended techniques for developers and the bug report/feature request guidelines.
General Usage and Information
The APIs for EVE Metrics are primarily offered in the XML format. This format should be fairly familiar to most EVE API developers, as the EVE API itself uses the same format.
The APIs can also be retrieved in JSON/JSONP formats using the .json extension and the callback parameter.
APIs are accessed at the /api/ root, using the URIs specified for each resource in the resource docs.
All APIs which take type/region parameters will accept multiple comma-seperated values (type_ids=34,35,36 for example) or single values (though note the parameter name is still plural).
Requests should be GET requests. Developer keys are not optional on some methods but can be omitted; however, the use of developer keys is recommended on all resources if your application is being distributed or otherwise is likely to make a lot of requests (See section below).
API Request Limits
To prevent high memory usage in processing your requests we limit the number of permutations of types and regions you can request in one HTTP request to the API. This limit is currently 25.
This means that for any request, the number of type IDs multiplied by the number of region IDs (or one if no region is specified) must be below 25. If you need more, you must make multiple requests, or consider using a snapshot or CSV dump. Most API information is available in these formats, so for larger batch operations you should always look to using these instead of the APIs where possible.
Batch Downloads
We recommend no more than 50 items are requested at a time for any API call. In situations where you want to retrieve a complete set of market orders, you should use the CSV dumps instead.
High Volume Applications
In cases where your application is being distributed and used by an audience in excess of 1,000 users, please contact us with information about your application. We like some warning just in case your app goes mad and we have to temporarily throttle it to stop it killing the server, and we may have some notes on how you could improve performance of your app and optimise the number of calls you're making to the APIs.
Developer Keys and Contact Information
Developer keys are required for only the order method, but are highly recommended for all methods; these allow us to track application usage of APIs so we can contact you if there are problems with the application (ie not caching results or making requests at a huge rate). For this reason it is also important to check your user account has a valid email address specified- we will try and contact you there first, but we may have to disable your application's access if we do not receive a response within a reasonable amount of time.