Open mumbleskates opened 7 years ago
/characters/{character_id}/
now reflects corporation_id
, which is great. The XML API is still required to get exact time of death, but only once (or rather, once per biomass in the event a character is revived).
Is this a feature that's likely to be looked at? Seems that at the moment the character endpoint will return a 404 with a message that the character is deleted, but the corporation history shows no entry for Doomheim.
Previous APIs reflected the membership of a character in Corporation 1000001 (Doomheim), and the time which they joined.
Example:
https://api.eveonline.com/eve/CharacterInfo.xml.aspx?characterID=90000009 https://crest-tq.eveonline.com/characters/90000009/ https://esi.tech.ccp.is/latest/characters/90000009/?datasource=tranquility
The old XML API indicates that the character is in Doomheim, as well as what date they joined (their date of biomass). There does not appear to ever be an attendant record or recordID for the transition to Doomheim, but the information is clearly there and definitely useful.
CREST admits that the character is a member of Doomheim but does not reflect the date.
ESI makes no admission of the character's status at all. The only reliable way to check if characters have been biomassed is to utilize the
/search/
endpoint with their name and see if the result is missing or of the wrong ID. (It does, however, tell you their birthday: information already available from the ESI employment-history endpoint.)Either of the following solutions would be great:
Reflect the current corporation ID and date joined, information which always exists, in
/characters/{character_id}/
Include entries for the transition to Doomheim in
/characters/{character_id}/corporationhistory/
. This may be awkward if no such record rows actually exist, but is an ideal solution.