Toggle menu
Toggle preferences menu
Toggle personal menu
Not logged in
Your IP address will be publicly visible if you make any edits.

User:Drakken Keisterbane/CREST: Difference between revisions

From EVE University Wiki
mNo edit summary
Rayanth (talk | contribs)
m Rayanth moved page User:Drakken keisterbane/CREST to User:Drakken Keisterbane/CREST: Automatically moved page while merging the account "Drakken keisterbane" to "Drakken Keisterbane"
 
(3 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{WIP}}
 


The Carbon RESTful (CREST) HTTP API is a ''read and write'' API to the EVE Universe. It gives the ability to interact with the game cluster in an effective manner from clients and applications other than the EVE game client. Although not all CREST endpoints been released yet, there are plenty of useful public endpoints available at this time, with more being released on a regular basis.
The Carbon RESTful (CREST) HTTP API is a ''read and write'' API to the EVE Universe. It gives the ability to interact with the game cluster in an effective manner from clients and applications other than the EVE game client. Although not all CREST endpoints been released yet, there are plenty of useful public endpoints available at this time, with more being released on a regular basis.
Line 53: Line 53:
Note that violation of the specified rate limits may result in an IP ban from CREST.
Note that violation of the specified rate limits may result in an IP ban from CREST.


==Entry Points==
 
===Entry Points===


There are two root entry points available for CREST, one for '''Tranquility''' and one for the '''Singularity''' test server (Sisi). The entry points below are accurate as of the time of writing.
There are two root entry points available for CREST, one for '''Tranquility''' and one for the '''Singularity''' test server (Sisi). The entry points below are accurate as of the time of writing.




Line 65: Line 65:




==Endpoints==


===Notes===
===Notes===
Line 79: Line 77:


In addition, each page will always have a '''next''' JSON object, which will contain a name/value pair, named '''href''' whose value is a URI that can be used to reach the next page of data in the collection.
In addition, each page will always have a '''next''' JSON object, which will contain a name/value pair, named '''href''' whose value is a URI that can be used to reach the next page of data in the collection.


====Common Object Structures====
====Common Object Structures====


(todo: fill this in with common object structures to reduce how many times things need to be written down)
(todo: fill this in with common object structures to reduce how many times things need to be written down)
==Endpoints==


===Alliances and Corporations===
===Alliances and Corporations===


====Alliance Info (all)====
====Alliance Info (all)====
Line 105: Line 110:
* '''totalCount''': A JSON int, which indicates the number of objects in the collection.
* '''totalCount''': A JSON int, which indicates the number of objects in the collection.
* '''pageCount_str''': A JSON string, which indicates the total number of pages in this collection.
* '''pageCount_str''': A JSON string, which indicates the total number of pages in this collection.


====Alliance Info (single)====
====Alliance Info (single)====
Line 155: Line 161:


===Other===
===Other===
====Killmail====
To obtain the required killmail hash for the killmail endpoint, you can use the formula below:
'''killmailHash''' = '''sha1(''victimCharacterID'' + ''attackerCharacterID'' + ''shipTypeID'' + ''killTime'')'''
'''Note''': All variables in this formula are ''strings'', and adding them in this way represents ''concatenation'', not addition of the ids as integers.
Where the following is true:
* '''victimCharacterID''': The character id of the victim, as a string.
* '''attackerCharacterID''': The character id of the attacker that got the final blow. If the attacker with the final blow is an NPC (characterID == 0), this is the string "None" instead.
* '''shipTypeID''': The type id of the victim's ship.
* '''killTime''': The time the kill occurred, as a 64-bit timestamp (read unix timestamp * 10,000,000).


=External Resources=
=External Resources=