|
Author |
Thread Statistics | Show CCP posts - 7 post(s) |
|
CCP Phantom
C C P C C P Alliance
7226
|
Posted - 2016.11.08 18:40:47 -
[1] - Quote
There's a new API coming to EVE, called the ESI (EVE Swagger Interface). It's based on the OpenAPI Specification, is fully documented and will make your life easier if you choose to develop an application for EVE Online. It's been ramping up for a few months, and is currently serving up to 4.5 million requests a day.
Check out the exciting details in this new blog Introducing ESI - A new API for EVE Online!
CCP Phantom - Senior Community Developer
|
|
|
CCP Bartender
C C P C C P Alliance
75
|
Posted - 2016.11.08 19:42:56 -
[2] - Quote
Crashys wrote:When can we start test things?
It's running right now, you can go run test queries with the esi ui, no code needed. We'll be opening up most of the scopes tomorrow, once we've had an opportunity to assess the load overnight and make sure nothing needs shoring up. |
|
|
CCP Bartender
C C P C C P Alliance
75
|
Posted - 2016.11.09 10:08:31 -
[3] - Quote
Untelo1 wrote:Will there be wallet transactions via the new API?
That and wallet journal entries for both characters and corporations are extremely high on our priority list. I have some partial work done for the character wallet journals, there's some pain involved in presenting all the different types of journal entries (there's more than 200 of them ), but I'll figure something out. Once that's done corp wallet journals and transactions should follow quickly.
Colonel Mode wrote:Just quickly glancing over the EVE Swagger Interface and it doesn't appear there's any of the market orders that are available through CREST. Has it just not been added yet? Or am I looking in the wrong place?
Similarly high on our hit list and similarly work is already under way on it.
Mona Kasenumi wrote:The most important thing about the SSO is: - Players need to have the ability to revoque access whenever they want!
Today once someone have your access you can't do anything to stop then from gathering your data.
This is a HUGE issue that REALLY needs to be fixed!
This already exists but is not well presented. It's actually linked from the community page and can also be accessed with this URL: https://community.eveonline.com/sso. I'm hoping to get something more accessible into the launcher, but I won't expand too much on that now, or I'll be promising another teams engineering time and that's just impolite
Rivr Luzade wrote:Detail question: Will ESI have data end points for citadel markets and industry data points for the coming industrial complexes, among other things?
Structures in general are first class entities in ESI and we're expending a lot of brain power to make sure that authorized characters can access them without leaking information to unauthorized characters. When the market endpoints are released, there will be a solution in place for structures as well.
The same is true for industry endpoints, although they are not currently at the top of our priority list. If you'd like to make a case for them being higher priority you should totally join the #esi channel on the tweetfleet slack, we are coordinating with the community to prioritize these things, and most of that happens in tweetfleet |
|
|
CCP Bartender
C C P C C P Alliance
75
|
Posted - 2016.11.09 14:33:50 -
[4] - Quote
Querns wrote: While I'd like to see quite a bit of structure functionality, the most important thing in my mind is FUEL. Right now, the only tools we have to monitor fuel levels is a notification when the structure runs out of fuel.
That's actually not the case, for several months now the /corporations/corporationID/structures/ resource has been available in CREST. If you have starbase manager roles in the corp that owns the citadel, you can use that to see when your citadels fuel expires.
So that one will probably come later unless it end up being convenient to wrap into a unit work for other reasons. We're very focused on the XML API at the moment. |
|
|
CCP Bartender
C C P C C P Alliance
75
|
Posted - 2016.11.09 16:24:15 -
[5] - Quote
Piedro Nolm wrote:I am a bit worried.
How easy will it be to run an application that requires certain access rights from a developers local machine? SSO will not work locally due to the callback from the login server having no DNS name to return the call to, right?
Not having to deploy an application for live/integration testing or rapid protoyping is very important to me.
How will that be possible if the ESI API will not allow access with API Keys?
You can set the callback in your SSO client to localhost, and that'll let the browser callback to the local machine. Obviously you'll need something locally listening to get the key as it comes back, or you'll need to grab it out of the URL manually, whichever takes your fancy. Whatever technique you're currently using for CREST development will work exactly the same.
Piedro Nolm wrote:Also regarding the new EVE Portal APP:
If I am forced to use SSO, I can not monitor characters from multiple accounts, right? Each account would have a different SSO login.
That seems like a pretty big disadvantage, considering alpha clones are around the corner and people will likely use those in addition to their existing accounts.
ESI is specifically and deliberately a character oriented API. We will not be delivering account level information in ESI. So yes, if you want to monitor multiple characters from the same account you will have to add each one individually. |
|
|
CCP Bartender
C C P C C P Alliance
79
|
Posted - 2016.11.30 14:10:01 -
[6] - Quote
Jack Bladder wrote:Could you make it explicit that an api call is not yet supported? Spending a lot of time integrating to ESI only to get the following message is a big waste of my time and equally frustrating:
{"response": "not yet implemented", "error": "Invalid 200 response: should be array, is str"}
Please make it clear in the Implementation Note.
Can we have an ETA (however rough it is) on when character transactions will be supported? I would like to know if it worth waiting for it and keep working with the old XML API.
If that's the journal endpoint, it's tagged as a dummy endpoint. All endpoints are tagged as either "dummy" or "live". If that's coming from an endpoint tagged as live please file an issue on esi-issues so we can go fix it |
|
|
CCP Bartender
C C P C C P Alliance
79
|
Posted - 2016.11.30 16:58:23 -
[7] - Quote
They're the top level folders in the swagger UI, and they're listed as tags in the swagger.json. They're a bit of pre-launch cruft though TBH. We've also got a system for hiding partially completed endpoints, but it hasn't been applied backwards to all the endpoints that were specced out during the first few months of ESI development, while all the tooling was being made.
I'm talking with Snowdin now about making something a little more robust. |
|
|
|
|