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: A quick update to market orders

First post
Author
CCP Phantom
C C P
C C P Alliance
#1 - 2015-01-09 14:18:32 UTC  |  Edited by: CCP Phantom
Thanks to CCP FoxFour the improvements and work on the API and CREST continued despite Christmas and vacation time. With the Proteus release we will get additional information on market orders such as the order ID, the ID of the order location and more.

Check out CCP FoxFour's latest dev blog A quick update to market orders!

CCP Phantom - Senior Community Developer

CCP FoxFour
C C P
C C P Alliance
#2 - 2015-01-09 14:19:27 UTC
Simple yet hopefully useful. :D

@CCP_FoxFour // Technical Designer // Team Tech Co

Third-party developer? Check out the official developers site for dev blogs, resources, and more.

Max Kolonko
Caldari Provisions
Caldari State
#3 - 2015-01-09 18:23:34 UTC
and will we be able now to use:
url_to_sell_orders?type=type_id,
instead of
url_to_sell_orders?type=url_to_type

???
CCP FoxFour
C C P
C C P Alliance
#4 - 2015-01-09 18:23:54 UTC
Max Kolonko wrote:
and will we be able now to use:
url_to_sell_orders?type=type_id,
instead of
url_to_sell_orders?type=url_to_type

???


No, not yet.

@CCP_FoxFour // Technical Designer // Team Tech Co

Third-party developer? Check out the official developers site for dev blogs, resources, and more.

Cadiz Aragon
Brutor Tribe
Minmatar Republic
#5 - 2015-01-09 20:34:54 UTC
cool!. Is making a method available to access this data without having to go through SSO url redirection still in the works?
CCP FoxFour
C C P
C C P Alliance
#6 - 2015-01-09 20:52:43 UTC
Cadiz Aragon wrote:
cool!. Is making a method available to access this data without having to go through SSO url redirection still in the works?


Not for these market resources.

@CCP_FoxFour // Technical Designer // Team Tech Co

Third-party developer? Check out the official developers site for dev blogs, resources, and more.

Cadiz Aragon
Brutor Tribe
Minmatar Republic
#7 - 2015-01-09 21:12:29 UTC
CCP FoxFour wrote:
Cadiz Aragon wrote:
cool!. Is making a method available to access this data without having to go through SSO url redirection still in the works?


Not for these market resources.


hmm, I guess I'm missing how then to make access of this data outside of a webapp that would get the redirected url with the token from SSO. If I'm trying to make use of this data in a stand alone application, what's the best way to receive that token back from https://login-tq.eveonline.com/oauth/token/? I don't have a web server running at the url I've currently registered with my app.
Pete Butcher
The Scope
Gallente Federation
#8 - 2015-01-09 22:09:45 UTC
Cadiz Aragon wrote:
CCP FoxFour wrote:
Cadiz Aragon wrote:
cool!. Is making a method available to access this data without having to go through SSO url redirection still in the works?


Not for these market resources.


hmm, I guess I'm missing how then to make access of this data outside of a webapp that would get the redirected url with the token from SSO. If I'm trying to make use of this data in a stand alone application, what's the best way to receive that token back from https://login-tq.eveonline.com/oauth/token/? I don't have a web server running at the url I've currently registered with my app.


We had a discussion about it here https://forums.eveonline.com/default.aspx?g=posts&m=5376942#post5376942

http://evernus.com - the ultimate multiplatform EVE trade tool + nullsec Alliance Market tool

Cadiz Aragon
Brutor Tribe
Minmatar Republic
#9 - 2015-01-09 22:51:07 UTC
Pete Butcher wrote:


thanks!
brammator
SUB ZERO.
#10 - 2015-01-17 10:19:20 UTC  |  Edited by: brammator
1. It's not on TQ now, right?
2. Is this endpoint listed at root folder? Can't find it in crest-public and api-sisi lists.
3. Do you plan to implement /market/regionID/orders/buy/typeID/ instead of mixing path and parameter elements? Or this is some good scheme I don't understand yet?
4. Is there working oauth/verify endpoint on public-crest.eveonline.com and api-sisi.testeveonline.com, or I should stick to login.eveonline.com and sisilogin.testeveonline.com?

EDIT.

5. Could you add info about required scope to root list of endpoints?
CCP FoxFour
C C P
C C P Alliance
#11 - 2015-01-19 10:20:00 UTC
brammator wrote:
1. It's not on TQ now, right?
2. Is this endpoint listed at root folder? Can't find it in crest-public and api-sisi lists.
3. Do you plan to implement /market/regionID/orders/buy/typeID/ instead of mixing path and parameter elements? Or this is some good scheme I don't understand yet?
4. Is there working oauth/verify endpoint on public-crest.eveonline.com and api-sisi.testeveonline.com, or I should stick to login.eveonline.com and sisilogin.testeveonline.com?

EDIT.

5. Could you add info about required scope to root list of endpoints?



  1. Yes the changes on on TQ now.
  2. The market endpoint? You get it by going through the regions. See more about that here: https://developers.eveonline.com/blog/article/nom-nom-tastey-market-data
  3. No as that breaks the RESTful nature of the API.
  4. You should be using crest-tq.eveonline.com
  5. That will be in the auto generated documentation that I hope to get out next month.

@CCP_FoxFour // Technical Designer // Team Tech Co

Third-party developer? Check out the official developers site for dev blogs, resources, and more.

brammator
SUB ZERO.
#12 - 2015-01-19 18:24:49 UTC
Thanks for answers. However,

CCP FoxFour wrote:
(brammator)2. Is this endpoint listed at root folder? Can't find it in crest-public and api-sisi lists.

* The market endpoint? You get it by going through the regions. See more about that here: https://developers.eveonline.com/blog/article/nom-nom-tastey-market-data


you see, to develop or use third-party api library, I need this endpoint to be declared in some sort of list. Or just hardcode it as "crest.MarketEndpoint.region[1000000002].orders.buy(type = crest.href(587))"

I'd prefer first way. What is the point of having bunch of not-working-yet endpoints listed at root, but not having working and very demanded one?

CCP FoxFour wrote:
(brammator)4. Is there working oauth/verify endpoint on public-crest.eveonline.com and api-sisi.testeveonline.com, or I should stick to login.eveonline.com and sisilogin.testeveonline.com?

* You should be using crest-tq.eveonline.com


https://crest-tq.eveonline.com/oauth/token/?grant_type=refresh_token&refresh_token=(token skipped)

401 {"message": "Authentication needed, bad token", "key": "authNeeded", "exceptionType": "UnauthorizedError"}

https://crest-tq.eveonline.com/oauth/verify/

404 {"message": "The route /oauth/verify/ was not found", "key": "routeMissing", "exceptionType": "NotFoundError"}

same requests to https://login.eveonline.com/ working fine.

So, crest-tq/oauth/token/ isn't working and crest-tq/oauth/verify/ isn't present.

CCP FoxFour wrote:
(brammator)5. Could you add info about required scope to root list of endpoints?

* That will be in the auto generated documentation that I hope to get out next month.


I'd like to see it in root crest list too, for mapping automation.
CCP FoxFour
C C P
C C P Alliance
#13 - 2015-01-19 18:46:25 UTC
brammator wrote:
Thanks for answers. However,

CCP FoxFour wrote:
(brammator)2. Is this endpoint listed at root folder? Can't find it in crest-public and api-sisi lists.

* The market endpoint? You get it by going through the regions. See more about that here: https://developers.eveonline.com/blog/article/nom-nom-tastey-market-data


you see, to develop or use third-party api library, I need this endpoint to be declared in some sort of list. Or just hardcode it as "crest.MarketEndpoint.region[1000000002].orders.buy(type = crest.href(587))"

I'd prefer first way. What is the point of having bunch of not-working-yet endpoints listed at root, but not having working and very demanded one?


Third party libraries should always follow links. You shouldn't need to know the route for things. People who use the library should know they go from the root v3 to regions v1 to market v1. That or the client should be built from the auto generated documentation that is not out yet.

brammator wrote:

CCP FoxFour wrote:
(brammator)4. Is there working oauth/verify endpoint on public-crest.eveonline.com and api-sisi.testeveonline.com, or I should stick to login.eveonline.com and sisilogin.testeveonline.com?

* You should be using crest-tq.eveonline.com


https://crest-tq.eveonline.com/oauth/token/?grant_type=refresh_token&refresh_token=(token skipped)

401 {"message": "Authentication needed, bad token", "key": "authNeeded", "exceptionType": "UnauthorizedError"}

https://crest-tq.eveonline.com/oauth/verify/

404 {"message": "The route /oauth/verify/ was not found", "key": "routeMissing", "exceptionType": "NotFoundError"}

same requests to https://login.eveonline.com/ working fine.

So, crest-tq/oauth/token/ isn't working and crest-tq/oauth/verify/ isn't present.


The SSO links should be included in the root of the API, https://crest-tq.eveonline.com/

See: "authEndpoint": {"href": "https://login-tq.eveonline.com/oauth/token/"}


brammator wrote:

CCP FoxFour wrote:
(brammator)5. Could you add info about required scope to root list of endpoints?

* That will be in the auto generated documentation that I hope to get out next month.


I'd like to see it in root crest list too, for mapping automation.


It will be.

@CCP_FoxFour // Technical Designer // Team Tech Co

Third-party developer? Check out the official developers site for dev blogs, resources, and more.

brammator
SUB ZERO.
#14 - 2015-01-19 22:31:30 UTC
CCP FoxFour wrote:


Third party libraries should always follow links. You shouldn't need to know the route for things. People who use the library should know they go from the root v3 to regions v1 to market v1. That or the client should be built from the auto generated documentation that is not out yet.



Perhaps it's my low english skill, but that's exactly what I'm asking for: link from root to that endpoint. I don't see it in root, I don't know how to build path to it programmatically, only how to hardcode it.