EVE Information Portal

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.



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!

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.

Well, now people will ask to register all 3 char from an account (and even that you can't verify since you don't have something that link them together), and they'll also ask a screenshot from the character selection page (like some corp already do lol)

i'd say, i'm fine with that change, but I also like to have some account data we currently have, like "subscription time left" (I don't believe there is any other relevant information account wide except the character list).

But we still need to register applications under https://developers.eveonline.com/applications , right.
When will we be able to do then, because atm I only see the option to create CREST and author only. No esi option atm

So I was curious about what Ariea Thellare stated about the endpoints for ESI not being available and did some digging.

Some of the endpoints are available. If you go to the Developer Website and click to Create a New Application and then Select CREST Access, you will notice that all of the CREST Scope are in Camel Case (camelCaseExample) whereas the scopes for ESI are snake_case. At the bottom of the list, there are 9 scopes that are snake_case. One can assume that these are some of the new ESI Scopes? I have listed them below. So I am assuming that they are allowing you to sign up for ESI using the current CREST access UI and then use that ClientID and Secret Pair to Access ESI

• read_calender_events
• read_character_wallet
• read_clones
• read_contacts
• read_skillqueue
• read_skills
• read_structures
• respond_calendar_events
• structureVulnUpdate

Ok, good to know.
Thanks for the info. I didn't see these new scopes in crest

You can quite happily have multiple accounts signed in at the same time.

Due to the way it works, there's no real difference between characters on one account, and characters on multiple.

Just, when adding a new one, hit cancel. That lets you log in a new character.