These forums have been archived and are now read-only.

The new forums are live and can be found at https://forums.eveonline.com/

EVE Technology Lab

 
  • Topic is locked indefinitely.
 

Would like a timeline on when certain endpoints will be available
Author
Previous Topic Next Topic
Althaia Xylona
Xylona Technologies
#1 - 2016-12-22 09:18:08 UTC
As i am rewriting some EVE Online tools, and preparing an EVE Online API module for our upcoming Twitch bot, I would really appreciate a timeline in which CCP shows us when old style XML or CREST calls will be made publicly available in ESI.

It would be a hassle to call ESI with its authentication method for say wallet balance but then having to resort to old API calls for the actual wallet journal, for example. A timeline would allow me to decide when I can release certain tools or features in our bot.

I hope the far too long cache times on the XML API will be reworked in ESI to finally, at last, give us close to realtime data, which is imperative for live streaming, so I rather wait for ESI to grow and then release the goodies. Thanks.
Althalus Stenory
Flying Blacksmiths
#2 - 2016-12-22 12:26:52 UTC
Everything you want is there :
- https://esi.tech.ccp.is/latest/
- https://github.com/ccpgames/esi-issues/projects/1
- https://github.com/xxpizzaxx/esi-archive

There are -no- deadline afaik, but you just know that in ~17month, CREST and XML will be no more (assuming everything has migrate somehow on ESI)

EsiPy - Python 2.7 / 3.3+ Swagger Client based on pyswagger for ESI
Althaia Xylona
Xylona Technologies
#3 - 2016-12-22 15:31:07 UTC
Thank you for the links, Althalus Stenory.

So would you suggest, instead of waiting for ESI to include every call we had in XML and CREST, to use what we have right now and use the old API's too so we can write our software and gradually move over to ESI calls as they become available?
Messenger Of Truth
Butlerian Crusade
#4 - 2016-12-26 02:41:51 UTC
Althaia Xylona wrote:
Thank you for the links, Althalus Stenory.

So would you suggest, instead of waiting for ESI to include every call we had in XML and CREST, to use what we have right now and use the old API's too so we can write our software and gradually move over to ESI calls as they become available?


Yes do that, because there are still some questions about how ESI will support some of the existing functionality - for example the endpoints you can access with corporate API keys.

Trade Hub Price Checker: stop.hammerti.me.uk/pricecheck

Visit "Haulers Channel" in game for all matters courier-related.

Structure name/system API: stop.hammerti.me.uk/api