Pages: [1] 2 3 :: one page |
|
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
|
|
Soldarius
O C C U P Y Test Alliance Please Ignore
1539
|
Posted - 2016.11.08 19:11:10 -
[2] - Quote
First. This should be interesting. The 3 developers named are all people I have interacted with in the past and can confirm are easy to worth with and talk to. Their work using XML API and CREST has been nothing short of amazing. I'm looking forward to seeing what they can cook up.
http://youtu.be/YVkUvmDQ3HY
|
Crashys
Zonk Squad Hell's Pirates
11
|
Posted - 2016.11.08 19:15:46 -
[3] - Quote
When can we start test things? |
Aeon Haginen
Hogyoku Goonswarm Federation
0
|
Posted - 2016.11.08 19:31:24 -
[4] - Quote
Nice, finally something that should work :) But, will we be able to grant access to our data (player data) to some external app, the same way we are with keys (xml api)? Im refering to services like Evething, that is scraping data for lot of different users in batches and storing them for later use, instead of directly displaying data for only logged in users... |
|
CCP Bartender
C C P C C P Alliance
75
|
Posted - 2016.11.08 19:42:56 -
[5] - 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. |
|
Bruce Warhead
Fun is Pain
11
|
Posted - 2016.11.08 19:52:14 -
[6] - Quote
Welp time to start adjusting code from the WarpToMe Waitlist |
Ai Sakura
The Repository Curatores Veritatis Alliance
1
|
Posted - 2016.11.08 20:13:43 -
[7] - Quote
Well the only thing that stops me using CREST is the lack of account character listing that is possible via the XML API.
Will you be addressing this with ESI? |
Untelo1
V0LTA WE FORM V0LTA
10
|
Posted - 2016.11.08 20:53:29 -
[8] - Quote
Will there be wallet transactions via the new API? |
Colonel Mode
Noware Industries
2
|
Posted - 2016.11.08 21:40:32 -
[9] - Quote
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?
|
Blakslab
Go For Broke
0
|
Posted - 2016.11.08 23:19:41 -
[10] - Quote
I can't see in the API where I can get a list of character id's for the current login? Otherwise it looks like a healthy beginning. I can't help but wonder if you will add more features to entice devs to start using it though. |
|
Hamathar
Die Freischaffenden
0
|
Posted - 2016.11.09 00:18:10 -
[11] - Quote
looks awesome! hope things like industryjobs, blueprints and wallettransactions are added soon, cant wait to work with that api! Best thing is the documentation of the api! That was the main problem with crest imo thanks for investing time into the api-stuff!! |
Mona Kasenumi
Wrong Cyno Brothers of Tangra
17
|
Posted - 2016.11.09 01:28:33 -
[12] - Quote
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! |
GeekWarrior
Resilience. DARKNESS.
7
|
Posted - 2016.11.09 02:50:28 -
[13] - Quote
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!
Ahem... https://community.eveonline.com/support/third-party-applications/ |
Ima Wreckyou
The Conference Elite CODE.
3080
|
Posted - 2016.11.09 07:27:22 -
[14] - Quote
Interesting stuff! Did you use plain Kubernetes and built a custom build pipeline for the Docker images or did you use something like Openshift? Would be interesting to know how you account for stack/os updates if you built your own solution.
the Code ALWAYS wins
Elite PvPer, #74 in 2014
|
Rivr Luzade
Viziam Amarr Empire
2797
|
Posted - 2016.11.09 08:17:16 -
[15] - Quote
Detail question: Will ESI have data end points for citadel markets and industry data points for the coming industrial complexes, among other things?
UI Improvement Collective
My ridicule, heavy criticism and general pale outlook about your or CCP's ideas is nothing but an encouragement to prove me wrong. Give it a try.
|
|
CCP Bartender
C C P C C P Alliance
75
|
Posted - 2016.11.09 10:08:31 -
[16] - 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 |
|
Mona Kasenumi
Wrong Cyno Brothers of Tangra
17
|
Posted - 2016.11.09 12:30:30 -
[17] - Quote
Welp. Sorry. Is it new or what? Never saw it before lol |
Querns
GoonWaffe Goonswarm Federation
2588
|
Posted - 2016.11.09 14:07:09 -
[18] - Quote
CCP Bartender wrote: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
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. This is less than ideal, considering the requirement to burn three days worth of fuel use immediately when bringing a service module back online. You can't even reliably monitor fuel levels with the Assets endpoint, as you can't determine the flags of an item in a structure. Minimum Viable Product here is a list of the contents of the fuel hangar; as a bonus, having the currently online service modules included in the information would help too, but we could live without it in the short term.
On a less pressing note, a blind lookup for structure names would be nice. Unsolicited implementation suggestion follows. Perhaps generate a hexadecimal string or UUID corresponding to the structure from various identifying information of the citadel (and seeded, of course,) then pass that along as the ID in anything relevant (wallet journal entries, contracts, etc.) Then, have an endpoint similar to https://esi.tech.ccp.is/latest/#!/Universe/post_universe_names for resolving those uniquely identifying strings. This is (roughly) the tactic that's currently used for killmails in CREST, and it appears to be serving just fine.
This post was crafted by the wormhole expert of the Goonswarm Economic Warfare Cabal, the foremost authority on Eve: Online economics and gameplay.
|
|
CCP Bartender
C C P C C P Alliance
75
|
Posted - 2016.11.09 14:33:50 -
[19] - 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. |
|
Untelo1
V0LTA WE FORM V0LTA
10
|
Posted - 2016.11.09 15:32:08 -
[20] - Quote
CCP Bartender wrote: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.
I meant making transactions via the API.
|
|
Piedro Nolm
Red Federation RvB - RED Federation
0
|
Posted - 2016.11.09 15:44:06 -
[21] - Quote
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? |
Piedro Nolm
Red Federation RvB - RED Federation
0
|
Posted - 2016.11.09 15:59:01 -
[22] - Quote
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. |
|
CCP Bartender
C C P C C P Alliance
75
|
Posted - 2016.11.09 16:24:15 -
[23] - 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. |
|
Ariea Thellare
EVE University Ivy League
0
|
Posted - 2016.11.09 16:30:18 -
[24] - Quote
When will we be able to use it for our apps? If i create a new application on the developers site i can still only choose crest and auth only under connection type. there i would have to select esi, right? |
Piedro Nolm
Red Federation RvB - RED Federation
0
|
Posted - 2016.11.09 16:56:47 -
[25] - Quote
CCP Bartender wrote: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.
Thank you for your quick reply! I did not know about the localhost callback solution. Sounds good and I will give it a try.
Regarding my second point: I was thinking more about characters spread out over multiple accounts, not multiple characters on the same account. I can not login to multiple accounts at the same time, can I? Which means I will constantly have to logout/login if I want to monitor characters spread out over multiple accounts?
Cheers and happy coding! |
Ariea Thellare
EVE University Ivy League
0
|
Posted - 2016.11.09 17:29:10 -
[26] - Quote
I mean it works with oauth as far as i understand it. That mean you authenticate every char once by logging in and then you save the refresh token you get. With that you can do all the things. And you can just save the refresh tokens of multiple characters.
The "logging" is not an actual login in the classical sense it just gives you the token. That's why you also can't logout, you just delete the refresh token and then you would have to authenticate/login again to get a new one.
|
Altrue
Exploration Frontier inc Tactical-Retreat
2095
|
Posted - 2016.11.09 18:10:53 -
[27] - Quote
CCP Bartender wrote: 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.
Hold on, hold on.
The ability of API Keys to monitor ALL characters of the account, is a very important function in making sure that, at least on the account involved, there is no other character belonging to some enemy alliance.
Taking that functionality away is quite the big deal. And it will never reach feature parity with the API without that.
Signature Tanking Best Tanking
[Ex-F] CEO - Eve-guides.fr
Ultimate Citadel Guide - 2016 EVE Career Chart
|
GeekWarrior
Resilience. DARKNESS.
7
|
Posted - 2016.11.09 18:45:07 -
[28] - Quote
Mona Kasenumi wrote:Welp. Sorry. Is it new or what? Never saw it before lol
Not sure. It's been there for a little while. |
Untelo1
V0LTA WE FORM V0LTA
10
|
Posted - 2016.11.09 19:41:23 -
[29] - Quote
Altrue wrote:CCP Bartender wrote: 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.
Hold on, hold on. The ability of API Keys to monitor ALL characters of the account, is a very important function in making sure that, at least on the account involved, there is no other character belonging to some enemy alliance. Taking that functionality away is quite the big deal. And it will never reach feature parity with the API without that.
RIP Big Brother. |
Ai Sakura
The Repository Curatores Veritatis Alliance
1
|
Posted - 2016.11.09 21:07:40 -
[30] - Quote
Altrue wrote:CCP Bartender wrote: 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.
Hold on, hold on. The ability of API Keys to monitor ALL characters of the account, is a very important function in making sure that, at least on the account involved, there is no other character belonging to some enemy alliance. Taking that functionality away is quite the big deal. And it will never reach feature parity with the API without that.
Exactly...
CCP want to promote spying that's fine, but they don't want to make it easy for alliances/corps to catch the low hanging fruit that people try and use on the same account.
Character listings on APIs are used from checking people on recruitment, to authentication systems and CCPs continual refusal to recognize this, firstly with CREST and now with ESI is very frustrating especially considering they want to shut down the XML API.
It isn't feature parity when you neglect one of the most common use cases for the API. |
|
|
|
|
Pages: [1] 2 3 :: one page |
First page | Previous page | Next page | Last page |