Page 1 of 1


Posted: Fri Nov 18, 2016 07:04
by Redhouse ... ucing-esi/
The ESI API is a RESTful, SSO authenticated... read/write API

Once we replicate all current CREST and XML API functionality in ESI, we will be shutting down both services. We are targeting 18 months from the release of this blog to achieve functional equivalence and work with application developers to upgrade their applications
Will this be a challenge to implement for EDK? Any Thoughts?

Re: Swagger

Posted: Fri Nov 18, 2016 14:23
by prometh
It sure will be a lot of work. Luckily theres time. Since esi is very similar to crest it might be not too complicated. However the way how you set up killmail fetching will change completely duenl to SSO. Basically entering api keys by the admin will be a thing of the past, pilots / ceos / directors will have to log in using the eve account and grant permissions.
Currently whats needed is not available on TQ.

Cheers, Snitch

Re: Swagger

Posted: Sat Nov 19, 2016 22:20
by Salvoxia
What prometh said.
Since CCP plans to shut down the XML API as well as CREST, I envision some kind of gradual transition, beginning with replacing CREST with ESI to establish a codebase working well with ESI.
Since only public CREST endpoints are used, this can be done with comparatively little effort.
Once that's done and established, all XML API except for the killmails calls can be moved to ESI.
As a last step, the API key mechanism for fetching bulk killmails must be replaced with SSO and ESI.

Best Regards,