Pages: [1] 2 3 :: one page |
|
Author |
Thread Statistics | Show CCP posts - 27 post(s) |
|
CCP Phantom
C C P C C P Alliance
4441
|
Posted - 2014.06.18 14:37:00 -
[1] - Quote
CCP FoxFour comes with news regarding the API related to the industry changes coming with the Crius release on July 22nd. Due to those industry changes, access to various information via the API is going to change as well.
To give you and especially the fantastic developers of awesome third party tools and websites time to adjust to those changes, a new dev blog with detailed information is published. Those changes can currently be tested on the test server.
Read all about the industry related API changes in CCP FoxFour's latest dev blog Upcoming API Changes for Industry.
CCP Phantom - Senior Community Representative - Volunteer Manager |
|
|
CCP FoxFour
C C P C C P Alliance
3294
|
Posted - 2014.06.18 14:40:00 -
[2] - Quote
Mmmmm APIs. Nom nom. CCP FoxFour // Game Designer // @regnerba
|
|
Muscaat
EVE Markets
64
|
Posted - 2014.06.18 14:46:00 -
[3] - Quote
I am excite. |
Katrina Bekers
Rim Collection RC Sorry We're In Your Space Eh
207
|
Posted - 2014.06.18 14:53:00 -
[4] - Quote
Quote:(or my favourite suggestions char/stEVEJobs).
Stay foxfour, stay hungry. << THE RABBLE BRIGADE >> |
Mashie Saldana
BFG Tech
1096
|
Posted - 2014.06.18 14:54:00 -
[5] - Quote
Any particular reason why you still develop the API instead of adding these features into CREST? Mashie Saldana Dominique Vasilkovsky
|
Two step
Aperture Harmonics No Holes Barred
4685
|
Posted - 2014.06.18 14:56:00 -
[6] - Quote
I think the paging support for teams on public crest is broken, and it doesn't follow the usual pattern CSM 7 Secretary CSM 6 Alternate Delegate @two_step_eve on Twitter My Blog
|
Querns
GBS Logistics and Fives Support Goonswarm Federation
665
|
Posted - 2014.06.18 14:59:00 -
[7] - Quote
Most excellent -- I was hoping that the teams API would be functional before Crius, and lo, I see it is. This makes me very happy. Thanks to the API team for their hard work on this stuff! This post was crafted by a member of the Goonswarm Economic Warfare Cabal, the foremost authority on Eve: Online economics and gameplay. |
Querns
GBS Logistics and Fives Support Goonswarm Federation
665
|
Posted - 2014.06.18 15:01:00 -
[8] - Quote
Mashie Saldana wrote:Nice to see CREST is being used, when will it replace the API completely? Right now there's a pretty clear divide between the API and CREST. The API is used for character and corporation data -- stuff that requires authentication. CREST is used for eve universe data -- stuff that does not require authentication. I suspect that work is still underway to bring authentication to CREST, allowing new, authentication-based endpoints to be exposed, but for now I am happy to see all the goodies coming out of the project. This post was crafted by a member of the Goonswarm Economic Warfare Cabal, the foremost authority on Eve: Online economics and gameplay. |
Joshua Foiritain
Coreli Corporation Ineluctable.
831
|
Posted - 2014.06.18 15:05:00 -
[9] - Quote
Any chance well ever see our API access log available through the API? Manually going over IP's is effort, i want to outsource it to our website. DRUGS DRUGS DRUGS | Coreli Corporation, Serpentis Loyalists DRUGS DRUGS DRUGS | Small gang PVP & drug production DRUGS DRUGS DRUGS | Ship Replacement program DRUGS DRUGS DRUGS | Multiple roaming fleets per day |
Retar Aveymone
GoonWaffe Goonswarm Federation
457
|
Posted - 2014.06.18 15:07:00 -
[10] - Quote
Quote:Added corp/Facilities:
Listing all of a corporations facilities, including POS and Outpost You need a corporation key and a character with director, CEO, or factory manager roles to view this endpoint. This endpoint is cached for 1 hour.
I was not under the impression that someone without director or CEO could generate any type of corp key. Has that changed? |
|
|
Chribba
Otherworld Enterprises Otherworld Empire
12077
|
Posted - 2014.06.18 15:19:00 -
[11] - Quote
Nom nom nom noooom!
|
|
Steve Ronuken
Fuzzwork Enterprises Vote Steve Ronuken for CSM
3427
|
Posted - 2014.06.18 15:26:00 -
[12] - Quote
Querns wrote:Mashie Saldana wrote:Nice to see CREST is being used, when will it replace the API completely? Right now there's a pretty clear divide between the API and CREST. The API is used for character and corporation data -- stuff that requires authentication. CREST is used for eve universe data -- stuff that does not require authentication. I suspect that work is still underway to bring authentication to CREST, allowing new, authentication-based endpoints to be exposed, but for now I am happy to see all the goodies coming out of the project.
Exactly. Right now, there are three hurdles to get over wrt crest. The developer license (we have a draft version out. it has a few niggles which probably need to be ironed out), SSO (for crest auth), and the developers site, for managing the two preceeding things.
We pretty much /need/ the industry APIs, so for now, using the old form covers it.
In other news:
\o/ Woo! CSM 9! http://fuzzwork.enterprises/ Twitter: @fuzzysteve on Twitter |
Petra Hakaari
Probe Patrol Ixtab.
85
|
Posted - 2014.06.18 15:27:00 -
[13] - Quote
I don't know if its something about evemon, or api themselves, and its not intrinsecally related to industry but since i see we now will need corp api and ceo roles for that thingy, we might also get corp wallet with all their divisions and stuff too, i mean, would be nice :) |
Aebe Amraen
Dreddit Test Alliance Please Ignore
37
|
Posted - 2014.06.18 15:30:00 -
[14] - Quote
I think I remember mention of maybe getting a blueprints endpoint that would give information about all our owned blueprints--is that still a thing? |
Dread Nanana
Action Super Dupper Test Corp
10
|
Posted - 2014.06.18 15:37:00 -
[15] - Quote
The new API is a little less useful for invention outcomes.
Inventions really require completion status.. Fail/Success is quite important for them and having that information cached for 24h is somewhat less useful. Perhaps current jobs should return active jobs + completed jobs in the last 24h. That would avoid need to fetch history very often or at all.
The 1000 limit for history is of course better than the current one of 150 or so, which our industrial corp could overflow in a matter of hours.
If the API stays as is, is the history jobs endpoint cached globally or can 6 director keys result in effective 4h cache if queried in turn? (every 4h)
|
|
CCP FoxFour
C C P C C P Alliance
3294
|
Posted - 2014.06.18 15:47:00 -
[16] - Quote
Dread Nanana wrote:The new API is a little less useful for invention outcomes.
Inventions really require completion status.. Fail/Success is quite important for them and having that information cached for 24h is somewhat less useful. Perhaps current jobs should return active jobs + completed jobs in the last 24h. That would avoid need to fetch history very often or at all.
The 1000 limit for history is of course better than the current one of 150 or so, which our industrial corp could overflow in a matter of hours.
If the API stays as is, is the history jobs endpoint cached globally or can 6 director keys result in effective 4h cache if queried in turn? (every 4h)
The 1,000 limit is something we are hoping to expand to be even greater. We wanted to start with 1k for the test server however. CCP FoxFour // Game Designer // @regnerba
|
|
Querns
GBS Logistics and Fives Support Goonswarm Federation
665
|
Posted - 2014.06.18 15:48:00 -
[17] - Quote
Dread Nanana wrote:The new API is a little less useful for invention outcomes.
Inventions really require completion status.. Fail/Success is quite important for them and having that information cached for 24h is somewhat less useful. Perhaps current jobs should return active jobs + completed jobs in the last 24h. That would avoid need to fetch history very often or at all.
The 1000 limit for history is of course better than the current one of 150 or so, which our industrial corp could overflow in a matter of hours.
If the API stays as is, is the history jobs endpoint cached globally or can 6 director keys result in effective 4h cache if queried in turn? (every 4h)
I suspect the new API is not intended for getting information about currently installed jobs, but rather, it is intended for historical data. I'm guessing that the existing endpoint we currently use for industry jobs will still retain its shorter time (and lower result count.) This post was crafted by a member of the Goonswarm Economic Warfare Cabal, the foremost authority on Eve: Online economics and gameplay. |
Sentient Blade
Crisis Atmosphere
1270
|
Posted - 2014.06.18 15:49:00 -
[18] - Quote
It's a big ask, but is there any chance we could have the caching interval dropped even more? The reason I ask is that when I was making heavy use of the API for my industry, I wanted to put in [x] jobs, then I had to wait for the expiry before I could issue another request, then have my code verify that I had put in all the jobs I needed to put in.
This is one of those things which would really benefit the community if you could drop it down to either a very small (~5 minute) caching duration, or remove it completely. |
|
CCP FoxFour
C C P C C P Alliance
3294
|
Posted - 2014.06.18 15:52:00 -
[19] - Quote
Two step wrote:I think the paging support for teams on public crest is broken, and it doesn't follow the usual pattern
Just talked to CCP Tuxford, he is submitting a fix for the pagination issue. We don't plan on actually splitting it into multiple pages, but left a default value in there. So total page count should be 1.
What do you mean it doesn't follow the usual pattern? CCP FoxFour // Game Designer // @regnerba
|
|
Querns
GBS Logistics and Fives Support Goonswarm Federation
665
|
Posted - 2014.06.18 15:53:00 -
[20] - Quote
On an unrelated note -- could I request that a timestamp parameter be added to the teams CREST endpoint that returns only entries with a creationTime greater than the timestamp? This would be useful for applications that wish to locally store the teams data for perusal and other generically nefarious ends.
It's not required for functionality, obviously, but it would be convenient. This post was crafted by a member of the Goonswarm Economic Warfare Cabal, the foremost authority on Eve: Online economics and gameplay. |
|
|
CCP FoxFour
C C P C C P Alliance
3294
|
Posted - 2014.06.18 15:54:00 -
[21] - Quote
Dread Nanana wrote:The new API is a little less useful for invention outcomes.
Inventions really require completion status.. Fail/Success is quite important for them and having that information cached for 24h is somewhat less useful. Perhaps current jobs should return active jobs + completed jobs in the last 24h. That would avoid need to fetch history very often or at all.
The 1000 limit for history is of course better than the current one of 150 or so, which our industrial corp could overflow in a matter of hours.
If the API stays as is, is the history jobs endpoint cached globally or can 6 director keys result in effective 4h cache if queried in turn? (every 4h)
Also I will ask about the success/failure thing. :) CCP FoxFour // Game Designer // @regnerba
|
|
Skutter Midumulf
Red Federation RvB - RED Federation
0
|
Posted - 2014.06.18 16:13:00 -
[22] - Quote
CREST should make transitions like this much easier as it's support for explicit representations (http://web.archive.org/web/20130103002534/http://wiki.eveonline.com/en/wiki/CREST_Documentation#Representations) means that old and new APIs can co-exist while apps migrate and then requests for old representations can return errors after the migration period without requiring new endpoints or confusing old apps with new data formats.
It's great to see the REST in CREST being useful! |
Bertrand Prout
Sunday Sessions
50
|
Posted - 2014.06.18 16:25:00 -
[23] - Quote
With these changes, will it be possible to retrieve Reverse Engineering jobs from with the API? |
Querns
GBS Logistics and Fives Support Goonswarm Federation
665
|
Posted - 2014.06.18 16:37:00 -
[24] - Quote
A small bug report with the team specialties CREST endpoint: It looks like specialty ID #40 is missing its label.
http://i.imgur.com/mFMkzoS.png This post was crafted by a member of the Goonswarm Economic Warfare Cabal, the foremost authority on Eve: Online economics and gameplay. |
|
CCP FoxFour
C C P C C P Alliance
3294
|
Posted - 2014.06.18 16:41:00 -
[25] - Quote
Known issue. :) Thank you though! :D CCP FoxFour // Game Designer // @regnerba
|
|
Imperator Universitas
Epsilon Inc
0
|
Posted - 2014.06.18 16:42:00 -
[26] - Quote
Heya folks, I was reading this over. I know everything is changing, but I think it'd be a pretty good idea to embed a new tag in the current XML for the replacement of the current call. You could also embed a text message with the sunset date of the current call.
That way when you are debuging your tools {if you are doing it properly} you will see both; that the XML feed you pulled contains helpful info on what you should be looking up, and what time you have to do it by.
If your parser behaves like it's supposed to, an extra tag will be ignored by execution code, but using your debugger or a full display you'll see it. If it breaks someone's tool, I'll be honest, that code was garbage.
Just a thought... --Imp |
|
CCP FoxFour
C C P C C P Alliance
3294
|
Posted - 2014.06.18 16:43:00 -
[27] - Quote
Skutter Midumulf wrote:CREST should make transitions like this much easier as it's support for explicit representations (http://web.archive.org/web/20130103002534/http://wiki.eveonline.com/en/wiki/CREST_Documentation#Representations) means that old and new APIs can co-exist while apps migrate and then requests for old representations can return errors after the migration period without requiring new endpoints or confusing old apps with new data formats.
It's great to see the REST in CREST being useful!
Yes! We are using that in several places, most notably the tournaments realtime resource has two versions. The whole time we were talking about what we should do for the API we were thinking "god this would be easier in CREST" >.< CCP FoxFour // Game Designer // @regnerba
|
|
Meytal
School of Applied Knowledge Caldari State
435
|
Posted - 2014.06.18 16:43:00 -
[28] - Quote
By any chance is it possible to adjust the 24 hour timers to be slightly less, say 23 or 23.5 hours? Then we can have timers set for 24 hours and it won't depend on client/network/server latency for us to get a real 24 hour report, since that's a really nice, round number.
|
|
CCP FoxFour
C C P C C P Alliance
3294
|
Posted - 2014.06.18 16:51:00 -
[29] - Quote
Meytal wrote:By any chance is it possible to adjust the 24 hour timers to be slightly less, say 23 or 23.5 hours? Then we can have timers set for 24 hours and it won't depend on client/network/server latency for us to get a real 24 hour report, since that's a really nice, round number.
When we set the timers for "24 hours" we tend to set them to 23.5 cause of that reason, we still say 24 though or people would be like "you said 23.5 so can you make it 23" and it's just a losing battle. CCP FoxFour // Game Designer // @regnerba
|
|
|
CCP FoxFour
C C P C C P Alliance
3294
|
Posted - 2014.06.18 17:00:00 -
[30] - Quote
OK so I straight up lied... well lie would mean I did it on purpose but the fact is I was completely wrong.
The jobs endpoint is cached for 15 minutes and the history one for 6 hours. Thats vs the 1 hour and 24 hours that I had said in the dev blog. /derp CCP FoxFour // Game Designer // @regnerba
|
|
|
|
|
|
Pages: [1] 2 3 :: one page |
First page | Previous page | Next page | Last page |