These forums have been archived and are now read-only.

The new forums are live and can be found at https://forums.eveonline.com/

EVE Technology Lab

 
  • Topic is locked indefinitely.
 

Crest Endpoints
Author
Previous Topic Next Topic
Dread Griffin
Pator Tech School
Minmatar Republic
#1 - 2016-05-31 17:55:13 UTC
I've created a standalone C# app that successfully authenticates (returns access and refresh tokens) for an arbitrary set of scopes.

Now... How do I see which endpoints each scope exposes? When i access the crest root with and without authentication I get the same result. So, I assume accessing the root doesn't give me the endpoints my tokens permit me to access.

Everything I've learned about this CREST structure is I'm not supposed to hard code the endpoints, but get them from the CREST itself... How can I do that for the authenticated endpoints?
Carbon Alabel
Gemini Talon
The Curatores Veritatis Auxiliary
#2 - 2016-05-31 20:07:12 UTC
You've got something wrong here: it's not about hardcoding the endpoints, it's about hardcoding the paths to endpoints..

If you dynamically load the path to an endpoint, send headers requesting a specific version of the endpoint, and watch for X-Deprecated headers, when (if) an endpoint changes its location or version, your app will be able to keep on working and notify you about the deprecation of the old version so that you can update your app to use the newer one.

You'll still be hardcoding your app to use a specific version of a specific endpoint. Unless your app is powered by a very advanced AI, it's simply not possible for it to make use of an arbitrary version of an arbitrary endpoint which you happen to have the scopes for. Don't look for endpoints which you can use with a scope, look for the scopes you need to use an endpoint.

As far as finding out which scopes you need for certain endpoints, you should take a look at the official Third-party docs and recent Third-party developer blogs and Patch notes.
Dread Griffin
Pator Tech School
Minmatar Republic
#3 - 2016-06-01 06:10:09 UTC
Thanks for the reply... I guess I thought that an endpoint and a crest url path were the same thing. I have read through a ton on those 3 sources already, but not completely.

I just know that https://crest-tq.eveonline.com/ provides many paths to the public data, and I was hoping something provided the paths to the authenticated data other than searching devblogs.

Thanks!
Carbon Alabel
Gemini Talon
The Curatores Veritatis Auxiliary
#4 - 2016-06-01 13:52:01 UTC
It's possible to get the paths to the private endpoints. The proper way to do so is to start at the root endpoint, then send an authenticated request to the decode endpoint, which will return the location of the character endpoint of the character the token belongs to, like https://crest-tq.eveonline.com/characters/93265215/

You can find links to various private endpoints there. You still have to make sure you have the required scopes to use the endpoints, and keep in mind some of them aren't available to third-party devs (yet).

Also, if you need any further help with this, the best way to get some is to join #devfleet on Tweetfleet Slack.
Dread Griffin
Pator Tech School
Minmatar Republic
#5 - 2016-06-01 15:02:11 UTC
Carbon Alabel wrote:
It's possible to get the paths to the private endpoints. The proper way to do so is to start at the root endpoint, then send an authenticated request to the decode endpoint, which will return the location of the character endpoint of the character the token belongs to, like https://crest-tq.eveonline.com/characters/93265215/

You can find links to various private endpoints there. You still have to make sure you have the required scopes to use the endpoints, and keep in mind some of them aren't available to third-party devs (yet).

Also, if you need any further help with this, the best way to get some is to join #devfleet on Tweetfleet Slack.

THANK YOU!Big smileBig smileBig smile

In everything I've read I've not come across this piece of info. I'll start playing with it asap.