EVE Technology Lab

 
4 Pages123Next pageLast page
 

Devsite blog: Introducing the ESI API

First post
Author
C C P Alliance
#1 - 2016-11-08 18:41:20 UTC
The EVE Swagger Interface (ESI) is a new framework developed by Team Tech Co to underpin the new ESI API.

This new blog from Team Tech Co. will dive a little deeper into the design and technical specifics of ESI, going to get into the base design of ESI to explain a few basic principles of what's going on behind the scenes.

Check out the blog Introducing the ESI API!

CCP Phantom - Senior Community Developer

#2 - 2016-11-08 19:15:58 UTC
This new API is awesome. Still where should we report bugs in it?

F.e.
Quote:
GET /corporations/{corporation_id}/icons/

returns
Quote:
{
"px64x64": "https://http://image.eveonline.com//Corporation/98446724_64.png",
"px128x128": "https://http://image.eveonline.com//Corporation/98446724_128.png",
"px256x256": "https://http://image.eveonline.com//Corporation/98446724_256.png"
}


Mean, icon url's are misformed
#3 - 2016-11-08 20:01:06 UTC  |  Edited by: NUBIARN
great stuff,

just started looking through the documentation for the endpoints, awesome stuff CCP. at last a api that doesn`t require a crystal ball to start working with, I'm impressed. and it looks likes the SSO work I did will still fundamentally work so cool, looking forward to getting to grips with this. Big smileBig smile one happy camper here.

oh did I mention the "try it" button which will create the endpoint link required, oh yes very nice, trial and error for devs gone.

link to documentation in case anyone missed it
Solyaris Chtonium
#4 - 2016-11-08 20:13:34 UTC
Looks awesome!

Do you have a road map of additional functionality you intend to add outside of the capabilities of the xml api/crest?
C C P Alliance
#5 - 2016-11-08 20:51:15 UTC
Phrynohyas Tig-Rah wrote:
This new API is awesome. Still where should we report bugs in it?

F.e.
Quote:
GET /corporations/{corporation_id}/icons/

returns
Quote:
{
"px64x64": "https://http://image.eveonline.com//Corporation/98446724_64.png",
"px128x128": "https://http://image.eveonline.com//Corporation/98446724_128.png",
"px256x256": "https://http://image.eveonline.com//Corporation/98446724_256.png"
}


Mean, icon url's are misformed


Thanks, those should all be fixed now.

For future bug reports, if you're on tweetfleet slack, the #esi channel is a great place to inform us.

We've also just now set up a public github repo for receiving and tracking ESI bugs, feel free to create issues there as appropriate: https://github.com/ccpgames/esi-issues

Cheers,

-SnowedIn

CCP SnowedIn // Distributed Systems Engineer // Team Tech Co // @CCP_SnowedIn

Warped Intentions
#6 - 2016-11-08 22:43:10 UTC
Yeay!! Another new API system which will be like the last one of very little documentation. How about you all finish one project before starting on another please? I know documentation isn't terribly great to be writing, but a little would go along way with CREST.
C C P Alliance
#7 - 2016-11-08 23:35:39 UTC
Minerva Arbosa wrote:
Yeay!! Another new API system which will be like the last one of very little documentation. How about you all finish one project before starting on another please? I know documentation isn't terribly great to be writing, but a little would go along way with CREST.


ESI can only return what the endpoint describes. It's a documentation-first API.

Check it out for yourself => https://esi.tech.ccp.is

CCP SnowedIn // Distributed Systems Engineer // Team Tech Co // @CCP_SnowedIn

C C P Alliance
#8 - 2016-11-08 23:38:12 UTC
Sashii Ohmiras wrote:
Looks awesome!

Do you have a road map of additional functionality you intend to add outside of the capabilities of the xml api/crest?


Thanks!

There's a trello board that we're keeping for wishlist/feature requests. If you want to toss the idea around in the #ESI tweetfleet channel, we're eager to hear community suggestions for what could enable some really cool apps (without breaking the game, ofc).

CCP SnowedIn // Distributed Systems Engineer // Team Tech Co // @CCP_SnowedIn

Tactical-Retreat
#9 - 2016-11-08 23:53:17 UTC  |  Edited by: Altrue
Best of luck for this "new" (kinda not but you know what I mean) project!

Eagerly waiting for the unleashing of the full ESI potential :)

Seriously though, you mentionned cool new features with a special attention put into not breaking the game... But what about existing XML API features that are already breaking the game?

For instance, the Silo contents endpoint impact on the viability of mobile Siphons.

Can we expect this endpoint to be ported into the ESI API? Will there be some kind of game designer oversight of new ESI features to prevent them from altering too much the viability of gameplay features?

Also, have your first like haha Blink

Signature Tanking Best Tanking

[Ex-F] CEO - Eve-guides.fr

Ultimate Citadel Guide - 2016 EVE Career Chart

C C P Alliance
#10 - 2016-11-09 00:17:52 UTC
Altrue wrote:
Best of luck for this "new" (kinda not but you know what I mean) project!

Eagerly waiting for the unleashing of the full ESI potential :)

Seriously though, you mentionned cool new features with a special attention put into not breaking the game... But what about existing XML API features that are already breaking the game?

For instance, the Silo contents endpoint impact on the viability of mobile Siphons.

Can we expect this endpoint to be ported into the ESI API? Will there be some kind of game designer oversight of new ESI features to prevent them from altering too much the viability of gameplay features?

Also, have your first like haha Blink


haha, thanks for the like ;)

we are working closely with Five-O to ensure any new ESI endpoints are cleared by them first. The feedback process so far has been amazing, very thorough and well reasoned responses to any questions/concerns we've have when putting together these new specs, based on XML and CREST.

as for your specific case with the silos and siphons, that's something we'll have to look at again when we transition that endpoint. from my point of view, I'm more interested in the types and structures of the response and request. the data that's actually returned, and the "how" that data is returned, isn't really interesting to ESI, and is something ESI tries to abstract away from (the "how" could change at any time, without ESI being affected).

CCP SnowedIn // Distributed Systems Engineer // Team Tech Co // @CCP_SnowedIn

Caldari State
#11 - 2016-11-09 03:52:33 UTC
Is it possible to post a list of end-points that are going to be in the final release?

Are you guys going to add a way to query the id number of more than just alliances, since you need an id number for most GETs.
Solyaris Chtonium
#12 - 2016-11-09 06:02:51 UTC
Wayne Donne wrote:
Is it possible to post a list of end-points that are going to be in the final release?

Are you guys going to add a way to query the id number of more than just alliances, since you need an id number for most GETs.


Have a look at the "search" endpoints. I believe they should provide what you're looking for.
Caldari State
#13 - 2016-11-09 08:37:58 UTC
Sashii Ohmiras wrote:
Wayne Donne wrote:
Is it possible to post a list of end-points that are going to be in the final release?

Are you guys going to add a way to query the id number of more than just alliances, since you need an id number for most GETs.


Have a look at the "search" endpoints. I believe they should provide what you're looking for.


Well right now, you can call:

https://crest-tq.eveonline.com/regions/
https://crest-tq.eveonline.com/inventory/groups/

and cascade into basically everything from there. I am curious if that kind of luxury will still exist in the new api.
Mouth Trumpet Cavalry
#14 - 2016-11-09 09:28:00 UTC  |  Edited by: YeuxVerts Belle
https://esi.tech.ccp.is/latest/#/ lists a lot of endpoints, but the dev blog seems to declare this as a work-in-progress. How much of this new API is operationnal ? Can we switch to it already ?

Also, AWESOME.

The above message presents my opinions on the topic at hand. If there is a conflict between my views and reality, consider reality to be correct until proven otherwise.

Ivy League
#15 - 2016-11-09 10:40:11 UTC
Thank you for this new API. I welcome the change, swagger makes everyone life easier, even if it kills pretty much all the API libraries. I can barely wait until you finish all the endpoints I need.

/universe/structures/{structure_id}/ actually returns some of the citadels locations, but, not all...
Would it be possible to return all of them? Unresolved locations is really frustrating for jEveAssets users...

Here is a few that does not work:
1009490997062
1012126598203
1012126599746
1013891262742
1013979539456
1014956811902
1020241029341
1021153704082
1021386123900
1021856392758
1021998044990
1022068012367
1022069057551
1022069543859
1022080938053
1022080939326
1022311385966
1980638578
355158289

Creator of jEveAssets - the asset manager

"Download is the meaning of life, upload is the meaning of intelligent life"

#16 - 2016-11-09 12:57:22 UTC  |  Edited by: Althalus Stenory
Got few questions too :

  • What is the purpose of the Live tag with all the other operations there ? Showing what's really implemented / finished ?

  • Just wondering, is the list of scope in the securityDefinitions complete ? I believe that it is, but as I don't really know swagger yet... :) .

  • Will we have to register an application to use the SSO again (like for CREST) ? Or do we just have to use the infos from the securityDefinitions object ?


Anyway, this is really cool that CCP now use a standard to expose its API :D (especially with a complete doc <3)
Thanks, and I really hope it will grow fast and fine with everything from both XML API and CREST

EsiPy - Python 2.7 / 3.3+ Swagger Client based on pyswagger for ESI

#17 - 2016-11-09 13:03:34 UTC
It is nice to see that this API has at least the basic documentation, however there are a lot of "Getting started" infos missing. Like: "What's a character-ID and how do I get one?"
A few examples would be really helpful here.

Not having a rate limit is a mistake. As someone who has developed a few bigger REST APIs I guarantee that you will have to change that in the future. I'd recommend to do it earlier than too late. It doesn't have to be limiting to the standard user, but there just has to be one for the "stupid" user that sends 20k requests/minute because "polling is the best way to get accurate data".

What I am really missing form this API are market price data. I can of course get those by running over thousands of accounts and their wallet, but then having this as a simple and clean API would be useful. At least the major trade-hubs would be great for price calculation tools.
#18 - 2016-11-09 14:26:05 UTC
Raw Matters wrote:
What I am really missing form this API are market price data.


According to the Trello board, market-related endpoints are already implemented and queued for deployment.
#19 - 2016-11-09 14:31:44 UTC
That sounds great! I'd love to hear more official details on that.
#20 - 2016-11-09 16:35:44 UTC
How do I join the community on Trello or Slack?
4 Pages123Next pageLast page
Forum Jump