EVE Technology Lab

ESI is actually quite stable. There are some end points that will respond with a 500 error, just wait half a second and then make the call again.

I did write loops into my script to reattempt the call if the HTTP Status Code is not 200. Generally the second call is successful and if not the second then the third. I have never had to go beyond the third call unless they took the endpoint down for maintenance, but then I just wrote a script that disables that call if it is down.

It is good practice to have a fall back in your code. ESI is still in development to a degree and is actively being worked on. What you have done should not be look at from the standpoint that ESI is unrealiable, from the viewpoint that it is forcing you to take the extra steps to ensure that your code is more reliable.

One should never rely on a single API if there are other options available. If able, code the fall back. All this does is make your application that much better.

So I made a separate thread without realizing this one existed: https://forums.eveonline.com/default.aspx?g=posts&t=509896&find=unread

TL;DR: ESI is incredibly unstable for me, I consistently get 502 (Bad Gateway) "Temporary Errors" and it usually takes on the order of a minute to get a call to go through successfully.

Another picture: http://imgur.com/a/7Hr31

Hell,

So I'm trying to use this API. I have to say that it's beautiful and nice. But where can I find which type id is which item? Also where can I find let's say recipe info? Or skill infos? And the last one is the market prices endpoint: what does that average_price mean? is it the average of selling and buying prices of all region? Is the only way to get the current price is to get all orders then order them by price?

Thanks in advance.

I have a plan in mind for a spreadsheet, but no idea how to make it work. And now their getting rid of xml api's so now I am waiting on more "How-TO" on this new api. Hopefully they can get it stable so we can play around with the new system.

Given the Calendar API end-points are cached server side, and return loads of duplicates for the same event (yes, it seems broken? https://github.com/ccpgames/esi-issues/issues/216) , can we please have more filtering parameters. I'm open to other ideas, but here is my use-case and problem with ESI currently:

At the moment to get the entries for your corp and alliance for a given time range (e.g. "my corp and alliance event for the last two weeks), one has to:

1. Call "/characters/{character_id}/calendar/ "
2. Get the earliest "event_id" from the JSON returned.
3. Either (walk forward from a known event) or; Walk backwards one request every >5 seconds at the time calling "/characters/{character_id}/calendar/?from_event" for "event_id - (X * )" until you find something at or before your start date.
4. terate over all responses calling "/characters/{character_id}/calendar/{event_id}/" for each (unique) event_id.
5. Check the "owner_type" is "corporation" or "alliance"
6. (Optional) sanity check the owner_id matches the expected corpID / allianceID.
7. Repeat 4->6 walking forwards on "/characters/{character_id}/calendar/?from_event" for the latest event_id seen until you reach the 'end date' of the range you care about.

Can we please have options to:

• Suppress duplicate event_id's from "/characters/{character_id}/calendar/"
• An "EventScope" parameter which allows us to only pull down (Corp | Alliance | Character | All).
• A "FromDate" (and ideally a "ToDate").
• A "maxResults" and 'page' parameter allowing a decent number (e.g. 250) events. and iterating over more if the query results in more than maxResults hits.

EXAMPLE:

/v2/characters/{character_id}/calendar/?scopes=Corporation,Alliance&fromDate=2017-02-20&toDate=2017-03-05&maxResults=10&page=2&noDupliates=yes

Would get a only the calendar entries owned by the Corp or Alliance of the character (without duplicate event_ids), between the two dates given, returning entries 11-20 out of however many may have found.

Is it possible to get the list of my industry jobs?

The issue was created back in December requesting this feature.

https://github.com/ccpgames/esi-issues/issues/165

Please references this issue for further information. In addition to that you can join Tweetfleet #esi room to ask additional questions.

Hoping to get an actual dev to confirm this, because so far the only people who answer the question have been other players (unless another player has a link to a dev post that says as such)... When I tell others they seem clueless and ask for a dev post to backup the claims, which I haven't been able to find...

In the dev post back on 2016-11-08 (https://community.eveonline.com/news/dev-blogs/introducing-esi/) it says "Once we replicate all current CREST and XML API functionality in ESI, we will be shutting down both services." however people have been saying that player level data is going to be stripped out of the new API, which doesn't sound like all current functionality...

meaning...

No longer seeing what characters are linked to an account. (people use that for low hanging fruit security)
No longer knowing if someone is Omega or Alpha (people use that for skill calculations, low hanging fruit security, etc.)
No longer knowing when an account is going to expire (people use that for off-line subscription monitoring)
etc...

So can a dev to answer if these rumors are true because like I mentioned above, the last thing I've seen posted by the devs on this is "Once we replicate all current CREST and XML API functionality in ESI, we will be shutting down both services." and every time someone talks about it the devs seem to ignore it like they don't want to answer the question because of what that could mean to everyone.

Beyond that, ESI looks like an awesome API, looking forward to more end-points being added!

Thanks!

Kelath Erebus

The answer to you all of your points is no. Yes they will eventually turn off the Crest and XML API's and that will likely be when ESI has reach parity with them, BUT some things that WILL be different about ESI is that account t level data will just not be included in the ESI. This is CCP's domain and that is the judgement call they have made. So what are some methods of getting around this?

1. There no longer a way to detect how many characters are on an account. And unfortunately no work around d has been thought of nor will it be.

2. Skill calculation based on Account Type. Give the user the freedoms to flip flop between the two to see the affects on his skill queue. In addition, implants are not available Le either, so build a page where the user can input the implants that he currently fly has in.

3. As Car Hark was pointed out, there are no account expirations anymore. Just downgrades to Alpha status. So this point is no longer relevant.

You ask for links to all this information. My answer is a multi part

If you want to know this information like I do, monitor Reddit. That is prolly your best source of information.
Get on Slack and Join tweetfleet and then join the the rooms #devfleet & #esi
- The devs are here more than on the forums

Monitor twitter, YouTube, hit up a CSM, etc.

Fly safe and o7

hi friends. I am looking for an ESI alternative for the info available here:

https://api.eveonline.com/eve/SkillTree.xml.aspx

in other words - a global list of skills, unrelated to any characters. Is this info avaiable via ESI?

Thanks in advance,
-Z