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.
 

EVE Apis - Wrapping my Head around

First post
Author
Previous Topic Next Topic
Bh0di
Deep Core Mining Inc.
Caldari State
#1 - 2015-08-07 22:35:29 UTC  |  Edited by: Bh0di
Hi Guys,

i'm having a hard time wraping my head around the EVE-APIs.
I'm aware of the Wiki, the Dev-Blog, this forum, the searchfunction and google... but maybe i'm just a bit stupid.

Could you give me hint with the differences between the three APIs (i hope i didn't overlook a fourth) :

- XML EVE Api
- Public CREST
- SSO Auth CREST

What are the typical usecases?

What i understood so far:
- XML EVE Api
Static Data, and with the API-Key & ID character information like skills.
- Public CREST
With the MarketDataOrder-Change (Buy/Sell available) the new "hot"-API. What else than marketdata?
- SSO Auth CREST
IDK - for what is this good?

Thank you guys..

*Edit:*
The infos so far about the apis, 09.08.2015
- XML EVE Api
Static Universe Data, with the API-Key here character information like skills, coorp etc.
Playerowned documentation: https://neweden-dev.com/API
- Public CREST
So far consists of static data, also char-data as well up-to-date MarketData (previously only accessable via auth-crest)
Hint:
Devblog Informations about "Marketdata only via auth-crest" here are out-dated and can be ignored.
Example: https://public-crest.eveonline.com/market/10000002/orders/sell/?type=https://public-crest.eveonline.com/types/34/
(Req/s) advantages of auth-crest are broken and do not apply to marketdata-req via auth-crest
Playerowned documentation: https://www.fuzzwork.co.uk/crestDocumentation.php

- SSO Auth CREST
utterly useless to this date and time
Aineko Macx
#2 - 2015-08-08 07:05:08 UTC  |  Edited by: Aineko Macx
The XML API provides quite a number of character and corporation level data endpoints. It is mostly NOT static.
See https://neweden-dev.com/API

CREST provides both static universe data as well as things like market history and orders, alliance and industry related data endpoints.
There are both unauthenticated and authentication requiring endpoints. Authentication can be done with different scopes, but currently the only available scope is "publicData" (the naming is a bit confusing because it DOES require auth).

The CREST SSO Auth (technically NOT a single sign-on but shared authentication) is a service on CCPs side that provides the mechanisms by which users can authorize third party apps to access their characters data via CREST (but with only publicData scope there is very little of that, most is just general dynamic universe data like market orders).

iveeCore 3.0: The PHP engine for industrial activities and CREST library
Bh0di
Deep Core Mining Inc.
Caldari State
#3 - 2015-08-08 07:31:25 UTC
Aineko Macx wrote:
The XML API provides quite a number of character and corporation level data endpoints. It is mostly NOT static.
See https://neweden-dev.com/API

CREST provides both static universe data as well as things like market history and orders, alliance and industry related data endpoints.
There are both unauthenticated and authentication requiring endpoints. Authentication can be done with different scopes, but currently the only available scope is "publicData" (the naming is a bit confusing because it DOES require auth).

The CREST SSO Auth (technically NOT a single sign-on but shared authentication) is a service on CCPs side that provides the mechanisms by which users can authorize third party apps to access their characters data via CREST (but with only publicData scope there is very little of that, most is just general dynamic universe data like market orders).


Hi @Aineko Macx,
first of all: Thank you for the the clarification about the XML API!
Is there a List of all CREST Endpoints and their auth status? (available without authetification, only with OAuth2 SSO Token Available)?

Bye!
Aineko Macx
#4 - 2015-08-08 09:00:12 UTC
You can use Steve's CREST documentation for the individual endpoints: https://www.fuzzwork.co.uk/crestDocumentation.php
AFAIK there is no programmatical way to determine if an endpoint requires auth and what scope other than trying to call it without...

iveeCore 3.0: The PHP engine for industrial activities and CREST library
Kali Izia
GoomWaffe
#5 - 2015-08-08 09:11:45 UTC
Currently all TQ endpoints are available on both authed and public CREST.
Market data used to require authentication but there are proxy and session pinning related issues that prevent you from actually taking advantage of the higher rate limit on authed CREST.

On Sisi the character stats endpoint is the only one that requires auth, but I think that's broken right now anyway.
Aineko Macx
#6 - 2015-08-08 09:27:56 UTC
Kali Izia wrote:
Currently all TQ endpoints are available on both authed and public CREST.

I just verified, order data for instance does require auth on TQ.

Quote:
Market data used to require authentication but there are proxy and session pinning related issues that prevent you from actually taking advantage of the higher rate limit on authed CREST.

Hm, using auth I can reach around 100 reqs/s without running into the rate limiter.

PS.:To prevent confusion, we should always say un-authenticated crest instead of public, because "publicData" is an auth scope ;)

iveeCore 3.0: The PHP engine for industrial activities and CREST library
Kali Izia
GoomWaffe
#7 - 2015-08-08 09:31:49 UTC
Aineko Macx wrote:

I just verified, order data for instance does require auth on TQ.

Nope, you just need to use public CREST URLs: https://public-crest.eveonline.com/market/10000002/orders/sell/?type=https://public-crest.eveonline.com/types/34/
Aineko Macx
#8 - 2015-08-08 09:46:28 UTC
Ah yes, indeed. Once I implemented auth in my lib i went with crest-tq.eveonline.com and never looked back...

iveeCore 3.0: The PHP engine for industrial activities and CREST library
Bh0di
Deep Core Mining Inc.
Caldari State
#9 - 2015-08-08 14:56:59 UTC
Since every Endpoint is available on public-crest, and the same ratelimits (req/s) between public crest and auth-crest apply... are there any benefits on auth-crest left? or is it - in this date and time - utterly useless?
Steve Ronuken
Fuzzwork Enterprises
Vote Steve Ronuken for CSM
#10 - 2015-08-08 18:17:26 UTC
It should be noted:

Market data does not require auth.

https://www.fuzzwork.co.uk/market/viewer/ is an example of it.

If you're getting errors due to requiring auth, you've probably not shifted the whole thing over to working on public crest.

Woo! CSM XI!

Fuzzwork Enterprises

Twitter: @fuzzysteve on Twitter
Aineko Macx
#11 - 2015-08-08 19:37:25 UTC
Steve Ronuken wrote:
If you're getting errors due to requiring auth, you've probably not shifted the whole thing over to working on public crest.

We need that hinted at dev-deblog. It's not clear what the future of authed CREST is. (To me at least, prolly Steve is privy to more information).

iveeCore 3.0: The PHP engine for industrial activities and CREST library