API (Killmails) - zKillboard/zKillboard GitHub Wiki

ATTENTION

Are you looking to get all the killmails as they happen? Check out Websocket or RedisQ.

If you're looking to fetch the entire killmail history in bulk, the zkillboard data is available at EVE Ref Data.

zKillboard provides an API that allows access to fetch all killmails held within the database using various filters.

Do not hammer the server with API requests. Be polite.
If you must do several requests in a row, please space them out as much as possible.
Please send 'Accept-Encoding: gzip' as header, to help save bandwidth.
Please send 'User-Agent: <something>' as a header. Replace <something> with your name, email, website etc. Example: User-Agent: https://example.com/ Maintainer: Bob [email protected]

Be reasonable with your requests. Most entities don't have new kills every single hour, keep this in mind while programming your utility.
When developing a tool, try caching the requests locally.

All IDs used with the API are CCP IDs
The API will deliver a maximum of 200 killmails per request.
'/w-space/' and '/solo/' can be combined with '/kills/' and '/losses/'
To get combined '/kills/' and '/losses/', don't pass either '/kills/' or '/losses/'
pastSeconds returns only kills that have happened in the past x seconds.
pastSeconds can maximum go up to 7 days (604800 seconds) and must be a multiple of 3600
iskValue will returns killmails that have a value equal to or greater than the value passed
Remember to finish with a / (Forward slash), requests without this will silently fail.
All modifiers can be combined in any order
If you do not pass /killID/ then you must pass at least two of the following modifiers. ''/w-space/'', '/solo/' or any of the '/xID/' ones. (characterID, allianceID, factionID etc.)
JSONP is available
The API has CORS set.
The modifier zkbOnly returns a very limited amount of data, including the killID, hash, points, and value of the kill. Everything else can be fetched using the killID + hash in your code.

''#'' is a number
''YmdHi'' is a timestamp in the following format: ''201201012300'' (2012-01-01 23:33)
''Y'' is a year in the following format: ''2012''
''m'' is a month in the following format: ''01''

/xml/ is no longer supported. All results are returned in json format
zkbOnly, no-attackers, no-items, asc, desc, json will result in a non-json error being thrown
multiple entity comma separated fetching
time based killmail ordering
/limit/#/
/startTime/YmdHi/
/endTime/YmdHi/

we removed things because abuse