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 Information Portal

 
  • Topic is locked indefinitely.
123Next pageLast page
 

Dev blog: Upcoming API Changes for Industry

First post First post
Author
Previous Topic Next Topic
CCP Phantom
C C P
C C P Alliance
#1 - 2014-06-18 14:37:43 UTC  |  Edited by: CCP Phantom
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 Developer
CCP FoxFour
C C P
C C P Alliance
#2 - 2014-06-18 14:40:14 UTC
Mmmmm APIs. Nom nom.

@CCP_FoxFour // Technical Designer // Team Tech Co

Third-party developer? Check out the official developers site for dev blogs, resources, and more.
Muscaat
EVE Markets
#3 - 2014-06-18 14:46:19 UTC
I am excite. Big smile
Katrina Bekers
A Blessed Bean
Pandemic Horde
#4 - 2014-06-18 14:53:08 UTC
Quote:
(or my favourite suggestions char/stEVEJobs).


Stay foxfour, stay hungry.

<< THE RABBLE BRIGADE >>
Mashie Saldana
V0LTA
New Eden Alliance 99013733
#5 - 2014-06-18 14:54:20 UTC  |  Edited by: Mashie Saldana
Nice to see CREST is being used, when will it replace the API completely?

How to win EVE
Two step
Aperture Harmonics
#6 - 2014-06-18 14:56:16 UTC
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
Science and Trade Institute
Caldari State
#7 - 2014-06-18 14:59:41 UTC
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 the wormhole expert of the Goonswarm Economic Warfare Cabal, the foremost authority on Eve: Online economics and gameplay.
Querns
Science and Trade Institute
Caldari State
#8 - 2014-06-18 15:01:23 UTC
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 the wormhole expert of the Goonswarm Economic Warfare Cabal, the foremost authority on Eve: Online economics and gameplay.
Joshua Foiritain
Coreli Corporation
Pandemic Legion
#9 - 2014-06-18 15:05:26 UTC
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.

The Coreli Corporation is recruiting.
Retar Aveymone
GoonWaffe
Goonswarm Federation
#10 - 2014-06-18 15:07:32 UTC
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
#11 - 2014-06-18 15:19:49 UTC
Nom nom nom noooom!

★★★ Secure 3rd party service ★★★

Visit my in-game channel 'Holy Veldspar'

Twitter @ChribbaVeldspar
Steve Ronuken
Fuzzwork Enterprises
Vote Steve Ronuken for CSM
#12 - 2014-06-18 15:26:38 UTC
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 XI!

Fuzzwork Enterprises

Twitter: @fuzzysteve on Twitter
Petra Hakaari
Stalking Wolfpack
#13 - 2014-06-18 15:27:52 UTC
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 :)

Because tities .
Aebe Amraen
Dreddit
Test Alliance Please Ignore
#14 - 2014-06-18 15:30:52 UTC
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
Doomheim
#15 - 2014-06-18 15:37:21 UTC
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
#16 - 2014-06-18 15:47:07 UTC
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 // Technical Designer // Team Tech Co

Third-party developer? Check out the official developers site for dev blogs, resources, and more.
Querns
Science and Trade Institute
Caldari State
#17 - 2014-06-18 15:48:30 UTC
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 the wormhole expert of the Goonswarm Economic Warfare Cabal, the foremost authority on Eve: Online economics and gameplay.
Sentient Blade
Crisis Atmosphere
Coalition of the Unfortunate
#18 - 2014-06-18 15:49:14 UTC
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
#19 - 2014-06-18 15:52:14 UTC
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 // Technical Designer // Team Tech Co

Third-party developer? Check out the official developers site for dev blogs, resources, and more.
Querns
Science and Trade Institute
Caldari State
#20 - 2014-06-18 15:53:25 UTC
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 the wormhole expert of the Goonswarm Economic Warfare Cabal, the foremost authority on Eve: Online economics and gameplay.
123Next pageLast page