EVE Technology Lab

So right now we are working with the XML API. I want to experimet more with CREST, but I cannot find a list of endpoints and what variable they require to be passed. Am I blind and it is posted somewhere, or are these just not documented.

To be more specific, I am looking for characterInfo and characterSheet XML API equivalent.

Thanks.

I am totally novice at programming to eve/cpp interfaces so take this with a grain of salt. Perhaps others thought about this in the same way I did.

Coming into this blind, I assumed Crest was replacing xml-api, which I assume is still the plan. It just has not progressed very far down this path. I assume that any current crest api's that overlap xml-api's came about because of enhancements and/or bug fixes to the various data backing the xml-api's which only makes sense to provide in the brave new world of SSO and json.

I think its safe to assume that any new api's will only come out in crest and existing xml-api's will continue to trickle in, leaving them deprecated.

I also made the mistake of considering SSO to only be of use to Crest. Hint: think of SSO, Crest and xml-api as three totally separate things, because they are. SSO != crest, crest != SSO. Crest and xml-api has a "uses" relationship with SSO. SSO has no relationship (isa, hasa, uses) to either of them.

CCP has upped the anti here for existing applications, especially those that were tightly coupled to the IGB by, well killing the IGB! I did realize that the xml-api's were not going away for a long time, and assumed that those being pushed out of game (no more "trust this site") were going to have to do the old gather those soon to be stale keys in as painless a way as possible from the users.

To my pleasant surprise CCP has put the KeyID/Code authentication mechanism to legacy status except for one single subscriber Account category call (namely Account->callList). All of the xml-api's except for this one, can now use the "access_token" obtained from the SSO authentication in-place of the legacy/deprecated KeyId/Code's.

In the java world , it is desirable to have some declared version where the deprecated code is no longer going to be supported, but in many cases it just would damage too many existing consumers and thus they stick around for ever. Xml-api may well fall into this category, however the idea, as a developer is ... if's it new code, by all means SSO, json where available, sso's access_token where not.

Thus ... a new era is born ... leading edge eve applications will be SSO, utilizing both crest and xmi-api.

eta:

Oh and I hear the winters are terrible in Creat