|
Author |
Thread Statistics | Show CCP posts - 5 post(s) |
|
CCP Guard
C C P C C P Alliance
|
Posted - 2011.07.29 14:41:00 -
[1]
Please check out CCP Elerhino's new dev blog about the contract API features due at the end of summer.
And if you have questions for CCP Elerhino and friends about the contents of the blog, leave them right here in the thread as always.
-CCP Guard
|
|
|
CCP Elerhino
Minmatar C C P C C P Alliance
|
Posted - 2011.07.29 17:30:00 -
[2]
Originally by: Zirse
Quote: member of the corporation but in the API we're locking it behind a corporation key which only directors and CEOs can create. This is a kind of a security measure in the sense that it prevents members from accidentally giving corporate information to a 3rd party.
Now maybe I'm misunderstanding here, but knowing how meta EVE gets, I don't think it'll be long before anybody who wants access to the corporation data will have it. Is there a way to only send corporate data to API keys associated with that corporation?
That's exactly what it will do if we keep it like this, this data will only be available to corporate keys.
CCP Elerhino CCP Software - API
|
|
|
CCP Elerhino
Minmatar C C P C C P Alliance
|
Posted - 2011.07.29 17:45:00 -
[3]
Originally by: Marcel Devereux I would love the ability to view historical data. Can you please provide a way to walk market orders, wallet transactions/journal, and contracts that are older than a month? This data doesn't change and you could write it out in month chunks to flat files and server it up. What do you say?
This is actually something we thought about doing instead of the get-latest approach we ended up with. A get-latest solution is what we wanted to do to begin with, the reason why we thought about doing a walking/paging solution was that the method we used in the market orders recently has holes in it. But fetching single items to fill the holes is a better solution because it's a very fast query (by ID) and for some items you might have to page through a mountain of items to get to the single one you need because the paged items would be ordered by creation date and the single items you need can get quite old.
But this is not final and is actually something we'd really like to see some discussion on here.
CCP Elerhino CCP Software - API
|
|
|
CCP Elerhino
Minmatar C C P C C P Alliance
|
Posted - 2011.08.08 10:27:00 -
[4]
Originally by: Callean Drevus Question Will the contract details & contents API be open to for every contract? That is, if you've got the ID, will you be able to get the data specific for that contract? Contract information is open pretty much by default, so I should think this is a possiblity.
As long as the authenticated character is a part of that contract in some way - yes and yes.
CCP Elerhino CCP Software - API
|
|
|
CCP Elerhino
Minmatar C C P C C P Alliance
|
Posted - 2011.08.08 11:04:00 -
[5]
Originally by: Ryomanni
Q. Will the contracts results include a weeks worth of contracts, rather than just outstanding and in progress? It would make it easier to record the contracts that are finished, failed, or rejected.
Q. Regarding the recent dev blog post, "We'll also have a separate page or a contractID parameter so that you can look up a single contract." - Will that work on finished contracts?
Q. I see an approximate one hour cachedUntil time on the test server data. Is it possible this cached time could be lessened so new contracts can be recorded more quickly?
Q. Does the "title" element of the XML hold the user defined contract description?
Q. I noticed there are contracts that have a dateAccepted value even though they have a status of "Outstanding" - should that be a blank string like the dateCompleted value is?
Q. Will there be any change to the "showContract" IGB JavaScript method so only a contractID is required, instead of also having to supply the solarSystemID? And if not, could each contract API row also include a solarSystemID (this would save having to look up the solarsystemID of the startStationID in the data dump).
The contract list will include items created within the last week as well as all outstanding and inprogress contracts. You'll be able to fetch any of your contracts (also finished contracts, yes) using a contractID parameter on the contract list page. Most likely we'll start with a 1 hour cache time, we'd of course like to get it down but as always we need to be careful when it comes to performance. The title element should hold the custom description, yes. We are currently looking at special cases in the date columns, the dateAccepted is one of them.
CCP Elerhino CCP Software - API
|
|
|
|
|