Third Party Developer Blog

rss Viewing archived items for May 2017


Caution: AccountStatus.xml.aspx Deprecated and Unreliable

Team Tech Co | 2017-05-26 16:50
Currently, the XML API endpoint /account/AccountStatus.xml.aspx is returning unreliable data. This endpoint has been officially deprecated since November 2016. Team Tech Co. has decided that this issue is not considered a "critical bug". As such, there are no plans to make changes to the endpoint to fix this issue (per our announcement here). The reasons we did not class it as such are: Account level information will not be available in ESI. Players receive notification e-mails directly from CCP if their non-recurring subscription is approaching expiry. This endpoint's original intent is no longer relevant, as players are not prevented from logging into EVE if their Omega status lapses. Despite being deprecated and unreliable, we will be leaving the endpoint active so as to not disrupt applications that would break if it ... read more

ESI Best Practices: Generating Code With Underscore Routes

CCP Bartender | 2017-05-08 16:00
This blog post is part of a series of blogs examining best practices for ESI development. Each blog will be published on the 8th of each month during the journey towards XML API and CREST’s termination date. The legacy APIs will be terminated on May 8th, 2018, or earlier if metrics signal a trivial level of usage. This blog explains best practices for autogenerating language specific clients from the ESI swagger spec. When generating code from one of the named routes (e.g. ), you may have noticed the resulting client library uses /latest as the version in all its URL calls. You can see why if you look at this fragment of the swagger spec from the above URL: { "basePath": "/latest", "host": "", "info": { "description": "An ... read more

Changes to the public citadel endpoint

CCP Bartender | 2017-05-05 15:07
Greetings all! On Tuesday 9th of May, Team Tech Co will be releasing a behavior change to the /universe/structures/ endpoint. This change will affect all versions of the endpoint, and although it will not change the specification of the endpoint (so you won't need to update your code), you may wish to know about how the behavior changed and why. Until now, this endpoint has been returning the structure ID’s of every structure that had the "public" entity on its ACL's allowed docking rights. This was done on the basis that such citadels are clearly visible in space and in the in-game structure browser, and thus matched information given in game. However, this is not quite correct. It is possible to add the "public" entity to one's ACL's, and then explicitly ban someone. Some of you may have noticed that if ... read more