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.
 

Devsite blog: Nom nom tasty market data!

First post First post
Author
Previous Topic Next Topic
Cadiz Aragon
Brutor Tribe
Minmatar Republic
#161 - 2014-12-22 04:16:21 UTC
Steve Ronuken wrote:
Thrad Markner wrote:
Super happy about this! One quick question: what is the "right" way to get the system that a buy/sell order is in? Obviously I can just parse the station name string (assuming it continues to be the case that systems never contain a space in their name...), but that feels rather wrong and un-RESTy



For now, parsing out the location id from the href, then looking it up in the SDE for the station, works.

It's far from an ideal situation.


Yeah, I kinda have a follow up question around this. What are we supposed to use as the "primary key" for resources / objects in CREST? Seems like the href is being used in this regard, but that can change at any point if they decide to change routes, and the 'name' property can also be changed at any point as they rebalance modules, etc. The SDE is built around the 64bit Id as the primary key for objects but that doesn't seem to be readily available in CREST without making some assumption on route URL construction which is precisely the thing that CCP is telling us not to do.
SJ Astralana
Syncore
#162 - 2015-01-08 10:17:51 UTC  |  Edited by: SJ Astralana
It's pretty screwed up that 3rd party devs are the only reliable source of information. I mean seriously, if an href can't possibly work, don't expose it. There are too many instances of additional calls made necessary due to a mongoloid sense of academic purity. If a friendly name is provided, it goes without saying that its canonical ID gets populated alongside it, except apparently in this case it has to be said anyway. WTF.

Hyperdrive your production business: Eve Production Manager

Steve Ronuken
Fuzzwork Enterprises
Vote Steve Ronuken for CSM
#163 - 2015-01-08 10:22:44 UTC
If you follow Foxfour on Twitter, you'll know that IDs are being added into the representation, in the next release.

Woo! CSM XI!

Fuzzwork Enterprises

Twitter: @fuzzysteve on Twitter
SJ Astralana
Syncore
#164 - 2015-01-08 10:32:09 UTC  |  Edited by: SJ Astralana
Steve Ronuken wrote:
If you follow Foxfour on Twitter, you'll know that IDs are being added into the representation, in the next release.


Yet more crucial information coming from a 3rd party dev not available or at best not discoverable on the official site. Reading 8 pages filled primarily with setup requests for the two posts that are relevant because the docs are dead on arrival is completely stupid.

Hyperdrive your production business: Eve Production Manager

Pete Butcher
The Scope
Gallente Federation
#165 - 2015-01-08 11:04:53 UTC
I have to agree with SJ Astralana. Note that there isn't even a list of available CREST endpoints anywhere on the dev site. If a person likes to start working with CREST, there is literally zero info about what can be done. We only have https://developers.eveonline.com/resource/crest which isn't much interesting and https://developers.eveonline.com/resource/crest/public-crest - seriously, a page named "public CREST" has literally 3 lines of text with two limits enumerated. If not https://neweden-dev.com/Main_Page there would not be a way to even start EVE 3rd party development.

The developers page is good at making announcements about new features and changes, but that's about it and it's a shame. Life would be a whole lot easier of neweden-dev was simply copy-pasted there.

http://evernus.com - the ultimate multiplatform EVE trade tool + nullsec Alliance Market tool
CCP FoxFour
C C P
C C P Alliance
#166 - 2015-01-08 11:28:03 UTC
SJ Astralana wrote:
Steve Ronuken wrote:
If you follow Foxfour on Twitter, you'll know that IDs are being added into the representation, in the next release.


Yet more crucial information coming from a 3rd party dev not available or at best not discoverable on the official site. Reading 8 pages filled primarily with setup requests for the two posts that are relevant because the docs are dead on arrival is completely stupid.


I have a dev blog in the system waiting for approval with details on this very change. So... yea... /shrug

@CCP_FoxFour // Technical Designer // Team Tech Co

Third-party developer? Check out the official developers site for dev blogs, resources, and more.
CCP FoxFour
C C P
C C P Alliance
#167 - 2015-01-08 11:30:20 UTC
Pete Butcher wrote:
I have to agree with SJ Astralana. Note that there isn't even a list of available CREST endpoints anywhere on the dev site. If a person likes to start working with CREST, there is literally zero info about what can be done. We only have https://developers.eveonline.com/resource/crest which isn't much interesting and https://developers.eveonline.com/resource/crest/public-crest - seriously, a page named "public CREST" has literally 3 lines of text with two limits enumerated. If not https://neweden-dev.com/Main_Page there would not be a way to even start EVE 3rd party development.

The developers page is good at making announcements about new features and changes, but that's about it and it's a shame. Life would be a whole lot easier of neweden-dev was simply copy-pasted there.


Improving our documentation is on my list for the beginning of this year. Actually, as stated in my last dev blog (https://developers.eveonline.com/blog/article/december-2014-third-party-developer-update), most the beginning of this year will be spent on behind the scene changes along with improving the support we offer you guys rather tan feature improvements to CREST of the XML API itself.

@CCP_FoxFour // Technical Designer // Team Tech Co

Third-party developer? Check out the official developers site for dev blogs, resources, and more.
SJ Astralana
Syncore
#168 - 2015-01-08 11:59:20 UTC  |  Edited by: SJ Astralana
Anyone up for a comedy moment? The following uri works, which seems to imply the API itself does uri deconstruction.

https://crest-tq.eveonline.com/market/80006047/orders/sell//?type=https://api.eveonilne.com/types/34/

If you can't quite read it, eveonline is misspelled.

Hyperdrive your production business: Eve Production Manager

Pete Butcher
The Scope
Gallente Federation
#169 - 2015-01-08 12:13:54 UTC
SJ Astralana wrote:
Anyone up for a comedy moment? The following uri works, which seems to imply the API itself does uri deconstruction.

https://crest-tq.eveonline.com/market/80006047/orders/sell//?type=https://api.eveonilne.com/types/34/

If you can't quite read it, eveonline is misspelled.


I wonder why the buy/sell url don't follow the item history pattern:

https://crest-tq.eveonline.com/market/80006047/types/12345/history/

It would be much simpler to just return the https://crest-tq.eveonline.com/market/XYZ/types/ generic endpoint url for each region and append the type and data required, eg.:

https://crest-tq.eveonline.com/market/80006047/types/12345/buy/

http://evernus.com - the ultimate multiplatform EVE trade tool + nullsec Alliance Market tool
CCP FoxFour
C C P
C C P Alliance
#170 - 2015-01-08 12:15:51 UTC  |  Edited by: CCP FoxFour
Pete Butcher wrote:
SJ Astralana wrote:
Anyone up for a comedy moment? The following uri works, which seems to imply the API itself does uri deconstruction.

https://crest-tq.eveonline.com/market/80006047/orders/sell//?type=https://api.eveonilne.com/types/34/

If you can't quite read it, eveonline is misspelled.


I wonder why the buy/sell url don't follow the item history pattern:

https://crest-tq.eveonline.com/market/80006047/types/12345/history/

It would be much simpler to just return the https://crest-tq.eveonline.com/market/XYZ/types/ generic endpoint url for each region and append the type and data required, eg.:

https://crest-tq.eveonline.com/market/80006047/types/12345/buy/


Because the history resource was done by me while I was still wrapping my head around CREST. I plan on changing it to conform to the same pattern as the buy and sell orders.

Also, we never want you guys to construct URIs (again, the history thing is not done to CREST standards and thats my fault). If we did it your way, and kept with the idea of applications never constructing URIs, then we would have to provide a link to to every type for every region.

By doing it the way we have, we provide a link to every time once, and then a link to every regions buy orders. You then do the match with query parameters and never do any manipulation of the URI.

@CCP_FoxFour // Technical Designer // Team Tech Co

Third-party developer? Check out the official developers site for dev blogs, resources, and more.
Pete Butcher
The Scope
Gallente Federation
#171 - 2015-01-08 15:28:27 UTC
CCP FoxFour wrote:
Pete Butcher wrote:
SJ Astralana wrote:
Anyone up for a comedy moment? The following uri works, which seems to imply the API itself does uri deconstruction.

https://crest-tq.eveonline.com/market/80006047/orders/sell//?type=https://api.eveonilne.com/types/34/

If you can't quite read it, eveonline is misspelled.


I wonder why the buy/sell url don't follow the item history pattern:

https://crest-tq.eveonline.com/market/80006047/types/12345/history/

It would be much simpler to just return the https://crest-tq.eveonline.com/market/XYZ/types/ generic endpoint url for each region and append the type and data required, eg.:

https://crest-tq.eveonline.com/market/80006047/types/12345/buy/


Because the history resource was done by me while I was still wrapping my head around CREST. I plan on changing it to conform to the same pattern as the buy and sell orders.

Also, we never want you guys to construct URIs (again, the history thing is not done to CREST standards and thats my fault). If we did it your way, and kept with the idea of applications never constructing URIs, then we would have to provide a link to to every type for every region.

By doing it the way we have, we provide a link to every time once, and then a link to every regions buy orders. You then do the match with query parameters and never do any manipulation of the URI.


Sounds reasonable. Glad to see everything will be consistent. Do you know when this change will approx. be live?

http://evernus.com - the ultimate multiplatform EVE trade tool + nullsec Alliance Market tool
CCP FoxFour
C C P
C C P Alliance
#172 - 2015-01-08 15:43:48 UTC
Pete Butcher wrote:
CCP FoxFour wrote:
Pete Butcher wrote:
SJ Astralana wrote:
Anyone up for a comedy moment? The following uri works, which seems to imply the API itself does uri deconstruction.

https://crest-tq.eveonline.com/market/80006047/orders/sell//?type=https://api.eveonilne.com/types/34/

If you can't quite read it, eveonline is misspelled.


I wonder why the buy/sell url don't follow the item history pattern:

https://crest-tq.eveonline.com/market/80006047/types/12345/history/

It would be much simpler to just return the https://crest-tq.eveonline.com/market/XYZ/types/ generic endpoint url for each region and append the type and data required, eg.:

https://crest-tq.eveonline.com/market/80006047/types/12345/buy/


Because the history resource was done by me while I was still wrapping my head around CREST. I plan on changing it to conform to the same pattern as the buy and sell orders.

Also, we never want you guys to construct URIs (again, the history thing is not done to CREST standards and thats my fault). If we did it your way, and kept with the idea of applications never constructing URIs, then we would have to provide a link to to every type for every region.

By doing it the way we have, we provide a link to every time once, and then a link to every regions buy orders. You then do the match with query parameters and never do any manipulation of the URI.


Sounds reasonable. Glad to see everything will be consistent. Do you know when this change will approx. be live?


I will probably add the new resource in the February release and mark the existing one as deprecated at the same time. Then at a later date remove the existing one. Yay for proper deprecation support! :D

@CCP_FoxFour // Technical Designer // Team Tech Co

Third-party developer? Check out the official developers site for dev blogs, resources, and more.
CCP FoxFour
C C P
C C P Alliance
#173 - 2015-01-09 14:26:57 UTC
SJ Astralana wrote:
Steve Ronuken wrote:
If you follow Foxfour on Twitter, you'll know that IDs are being added into the representation, in the next release.


Yet more crucial information coming from a 3rd party dev not available or at best not discoverable on the official site. Reading 8 pages filled primarily with setup requests for the two posts that are relevant because the docs are dead on arrival is completely stupid.


See this dev blog for this "crucial information": https://developers.eveonline.com/blog/article/a-quick-update-to-market-orders

@CCP_FoxFour // Technical Designer // Team Tech Co

Third-party developer? Check out the official developers site for dev blogs, resources, and more.
Pete Butcher
The Scope
Gallente Federation
#174 - 2015-01-09 15:41:58 UTC
CCP FoxFour wrote:
SJ Astralana wrote:
Steve Ronuken wrote:
If you follow Foxfour on Twitter, you'll know that IDs are being added into the representation, in the next release.


Yet more crucial information coming from a 3rd party dev not available or at best not discoverable on the official site. Reading 8 pages filled primarily with setup requests for the two posts that are relevant because the docs are dead on arrival is completely stupid.


See this dev blog for this "crucial information": https://developers.eveonline.com/blog/article/a-quick-update-to-market-orders


Finally no more url parsingSmile Do we need to switch from application/vnd.ccp.eve.MarketOrderCollection-v1+json to another version?

http://evernus.com - the ultimate multiplatform EVE trade tool + nullsec Alliance Market tool
CCP FoxFour
C C P
C C P Alliance
#175 - 2015-01-09 15:59:11 UTC
Pete Butcher wrote:
CCP FoxFour wrote:
SJ Astralana wrote:
Steve Ronuken wrote:
If you follow Foxfour on Twitter, you'll know that IDs are being added into the representation, in the next release.


Yet more crucial information coming from a 3rd party dev not available or at best not discoverable on the official site. Reading 8 pages filled primarily with setup requests for the two posts that are relevant because the docs are dead on arrival is completely stupid.


See this dev blog for this "crucial information": https://developers.eveonline.com/blog/article/a-quick-update-to-market-orders


Finally no more url parsingSmile Do we need to switch from application/vnd.ccp.eve.MarketOrderCollection-v1+json to another version?


No as this is a backwards compatible change the version number was not bumped. :)

@CCP_FoxFour // Technical Designer // Team Tech Co

Third-party developer? Check out the official developers site for dev blogs, resources, and more.
Pete Butcher
The Scope
Gallente Federation
#176 - 2015-01-13 12:25:27 UTC
Small request - can we also have solar system id in the order data? Right now it takes a trip to the DB to query this based on the location id, and with the wacky location id mapping in the DB, it's really not fun.

http://evernus.com - the ultimate multiplatform EVE trade tool + nullsec Alliance Market tool
Darg Tarias
The Scope
Gallente Federation
#177 - 2015-03-08 06:05:30 UTC
Sign me up too please.


app: MarketAPITestApp3
id: fc3137f9064f43c18fc140edfec8313c
Jonas Altol
Viziam
Amarr Empire
#178 - 2015-03-31 13:27:42 UTC  |  Edited by: Jonas Altol
I would like access as well:

App: Jonas
id: 94f49094e7c546978c409782a2d72e0d
Kali Izia
GoomWaffe
#179 - 2015-03-31 13:35:46 UTC
You don't need to sign up in this thread anymore, it's been live for awhile now.

Either log in to https://developers.eveonline.com/ (TQ) or http://developers.testeveonline.com/ (Sisi), create a new application with CREST Access, and add the publicData scope.
Jonas Altol
Viziam
Amarr Empire
#180 - 2015-03-31 13:41:34 UTC
Kali Izia wrote:
You don't need to sign up in this thread anymore, it's been live for awhile now.

Either log in to https://developers.eveonline.com/ (TQ) or http://developers.testeveonline.com/ (Sisi), create a new application with CREST Access, and add the publicData scope.


Thank you! Will this give me market data access - i.e., what this thread is about?