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.
 

EVE API and Public CREST discussion

First post First post First post
Author
Previous Topic Next Topic
CCP FoxFour
C C P
C C P Alliance
#61 - 2014-04-15 13:25:27 UTC
Verite Rendition wrote:
CCP FoxFour wrote:
I will have a chat with the design department and see how they feel about these being added.
Thank you, FoxFour.Smile


Seem to have approval to do this once I have some spare time.

@CCP_FoxFour // Technical Designer // Team Tech Co

Third-party developer? Check out the official developers site for dev blogs, resources, and more.
Two step
Aperture Harmonics
#62 - 2014-04-15 13:42:32 UTC
CCP FoxFour wrote:


  1. You are not the first to ask, so OK but not sure what you guys will do with them.
  2. Will continue looking.
  3. Will consider removing that.
  4. /me shrugs, thats where it is. I could do another join and add it to the pins as well... but thats going to be blank for most.
  5. Waypoints are pins, so yea seems so.


Man, if you keep this stuff up, I am going to almost feel bad about calling you SocksFour (*almost*)

CSM 7 Secretary CSM 6 Alternate Delegate @two_step_eve on Twitter My Blog
W0wbagger
Immortalis Inc.
Shadow Cartel
#63 - 2014-04-15 15:36:00 UTC  |  Edited by: W0wbagger
RE: PI

From a management/poco tax (stats :P ) POV - what planet the poco is on - would be nice - i.e. not just the system...

TBH that would be nice to see in game as well as from the assets list it doesnt say what planet it is either - so someone telling you p1 is configured one doesnt help you and you have to check all of them.

Appreciate this isnt in the API area but PLEASE let us batch modify pocos! (i.e. set tax rates for multiple pocos at once) it's a click fest if you want to change all of your tax rates on 10s of pocos.
ItsmeHcK1
Immortalis Inc.
Shadow Cartel
#64 - 2014-04-15 17:25:44 UTC  |  Edited by: ItsmeHcK1
1) Please add a typeID to the CharacterName/CharacterID API. Would save one or multiple calls depending on what type it is. (I always check char/corp/alliance, in that order, so it could theoretically cut down two-thirds of the calls for CharacterInfo/CorporationSheet.)

2) Data on character transfers would be very sexy. For example, I sell a character and the Characters API would return another rowset called 'oldCharacters' or something with dates of sale/biomass/whatever.

3) Station trade information. Knowing what was traded will make background checks so much fun.
Evanova Android
Traquenard Labs
#65 - 2014-04-15 21:57:34 UTC  |  Edited by: Evanova Android
CCP FoxFour wrote:

All of the following endpoints require the characters API key to have access to the asset list.

/char/PlanetaryColonies
/char/PlanetaryPins
/char/PlanetaryLinks
/char/PlanetaryRoutes

All of the endpoints will need characterID attribute, keyID, and vCode. You will then need planetID for all but the colonies endpoint.


What about the access mask? will there be another category or which category does that falls in?

Also, having the constellationID and solarSystemID of each planet in the PlanetaryColonies call would be nice.

Then, the dates contain "AM" but the usual API format is "yyyy-MM-dd HH:mm:ss".

Sorry for being annoying while I implement your stuff :-)

Evanova - The Android App for Eve Online
Steve Ronuken
Fuzzwork Enterprises
Vote Steve Ronuken for CSM
#66 - 2014-04-15 22:28:57 UTC
Evanova Android wrote:
CCP FoxFour wrote:

All of the following endpoints require the characters API key to have access to the asset list.

/char/PlanetaryColonies
/char/PlanetaryPins
/char/PlanetaryLinks
/char/PlanetaryRoutes

All of the endpoints will need characterID attribute, keyID, and vCode. You will then need planetID for all but the colonies endpoint.


What about the access mask? will there be another category or which category does that falls in?

Also, having the constellationID and solarSystemID of each planet in the PlanetaryColonies call would be nice.

Then, the dates contain "AM" but the usual API format is "yyyy-MM-dd HH:mm:ss".

Sorry for being annoying while I implement your stuff :-)



access mask of 2

Asset list.

Woo! CSM XI!

Fuzzwork Enterprises

Twitter: @fuzzysteve on Twitter
CCP FoxFour
C C P
C C P Alliance
#67 - 2014-04-16 08:45:34 UTC
ItsmeHcK1 wrote:
1) Please add a typeID to the CharacterName/CharacterID API. Would save one or multiple calls depending on what type it is. (I always check char/corp/alliance, in that order, so it could theoretically cut down two-thirds of the calls for CharacterInfo/CorporationSheet.)


Use the new ownerID endpoint, it's better and gives you groupID. :)

@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
#68 - 2014-04-16 15:32:02 UTC
I made a bit of a mistake and the PI endpoint is going to be delayed. Should hopefully be out late next week or the week after.
Hopefully.

@CCP_FoxFour // Technical Designer // Team Tech Co

Third-party developer? Check out the official developers site for dev blogs, resources, and more.
Berluth Luthian
Sebiestor Tribe
Minmatar Republic
#69 - 2014-04-16 21:18:33 UTC
Any update on the ability to query the mysteriously missing Battle Win/Loss transactions from corp members in the Dust Wallet?
CCP FoxFour
C C P
C C P Alliance
#70 - 2014-04-17 19:32:59 UTC
Berluth Luthian wrote:
Any update on the ability to query the mysteriously missing Battle Win/Loss transactions from corp members in the Dust Wallet?


No update sorry.

@CCP_FoxFour // Technical Designer // Team Tech Co

Third-party developer? Check out the official developers site for dev blogs, resources, and more.
iskflakes
#71 - 2014-04-18 12:42:19 UTC  |  Edited by: iskflakes
Is there any news on CREST? (Especially contact list reading/writing)

-
CCP FoxFour
C C P
C C P Alliance
#72 - 2014-04-18 12:52:19 UTC
iskflakes wrote:
Is there any news on CREST? (Especially contact list reading/writing)


No news sorry.

@CCP_FoxFour // Technical Designer // Team Tech Co

Third-party developer? Check out the official developers site for dev blogs, resources, and more.
Polarina
EVE University
Ivy League
#73 - 2014-04-18 20:18:34 UTC  |  Edited by: Polarina
It would be lovely if we could get the names of the hangar divisions for a corporation. Going for the generic names Division 1, Division 2, Division 3, etc., from invFlags is a bit dull. Definitely not user friendly.

Where are my clothes?
CCP FoxFour
C C P
C C P Alliance
#74 - 2014-04-18 20:24:49 UTC
Polarina wrote:
It would be lovely if we could get the names of the hangar divisions for a corporation. Going for the generic names Division 1, Division 2, Division 3, etc., from invFlags is a bit dull. Definitely not user friendly.


I thought we gave those out on the corporation sheet... we give out wallet names...

https://neweden-dev.com/Corporation/Corporation_Sheet

Do those always say div1 and such?

@CCP_FoxFour // Technical Designer // Team Tech Co

Third-party developer? Check out the official developers site for dev blogs, resources, and more.
qu1ckkkk
The Warp Core Stabilizers
#75 - 2014-04-18 20:27:48 UTC
CCP FoxFour wrote:
Polarina wrote:
It would be lovely if we could get the names of the hangar divisions for a corporation. Going for the generic names Division 1, Division 2, Division 3, etc., from invFlags is a bit dull. Definitely not user friendly.


I thought we gave those out on the corporation sheet... we give out wallet names...

https://neweden-dev.com/Corporation/Corporation_Sheet

Do those always say div1 and such?


Nah, they give the correct names as they appear in game, a least in my experience.

Proud developer of SeAT! A Simple Eve API & Corporation Management Tool.

Project Page: https://github.com/eveseat/seat
Querns
Science and Trade Institute
Caldari State
#76 - 2014-04-18 20:29:59 UTC
CCP FoxFour wrote:
Polarina wrote:
It would be lovely if we could get the names of the hangar divisions for a corporation. Going for the generic names Division 1, Division 2, Division 3, etc., from invFlags is a bit dull. Definitely not user friendly.


I thought we gave those out on the corporation sheet... we give out wallet names...

https://neweden-dev.com/Corporation/Corporation_Sheet

Do those always say div1 and such?

I tried this with my corp key, and I got the division names and the wallet divisions as I'd named them.

This post was crafted by the wormhole expert of the Goonswarm Economic Warfare Cabal, the foremost authority on Eve: Online economics and gameplay.
Polarina
EVE University
Ivy League
#77 - 2014-04-18 20:49:54 UTC  |  Edited by: Polarina
I must've been completely blind! I've been on the lookout for these names for quite a while now. And FoxFour, thank you for all these improvements you've been making to the API, very much appreciated.

On a unrelated note, is it possible to change /corp/Locations.xml.aspx so that it doesn't fail completely on invalid asset IDs? In the minute it takes me to fetch and process the assets list, someone undocks in a ship, invalidating one of the asset IDs. For me, that's a relatively frequent event.

Currently, when that happens, I repeatedly split the list of asset IDs I request into two halves and call the API again on those two lists. This usually results in 9 to 11 requests instead of just one that would've otherwise been required.

Where are my clothes?
CCP FoxFour
C C P
C C P Alliance
#78 - 2014-04-18 23:07:17 UTC
Polarina wrote:
I must've been completely blind! I've been on the lookout for these names for quite a while now. And FoxFour, thank you for all these improvements you've been making to the API, very much appreciated.

On a unrelated note, is it possible to change /corp/Locations.xml.aspx so that it doesn't fail completely on invalid asset IDs? In the minute it takes me to fetch and process the assets list, someone undocks in a ship, invalidating one of the asset IDs. For me, that's a relatively frequent event.

Currently, when that happens, I repeatedly split the list of asset IDs I request into two halves and call the API again on those two lists. This usually results in 9 to 11 requests instead of just one that would've otherwise been required.



O_O

Thats horrible... I shall add it to my list of things to look at... this is is very long...

@CCP_FoxFour // Technical Designer // Team Tech Co

Third-party developer? Check out the official developers site for dev blogs, resources, and more.
qu1ckkkk
The Warp Core Stabilizers
#79 - 2014-04-19 04:09:56 UTC
Polarina wrote:
I must've been completely blind! I've been on the lookout for these names for quite a while now. And FoxFour, thank you for all these improvements you've been making to the API, very much appreciated.

On a unrelated note, is it possible to change /corp/Locations.xml.aspx so that it doesn't fail completely on invalid asset IDs? In the minute it takes me to fetch and process the assets list, someone undocks in a ship, invalidating one of the asset IDs. For me, that's a relatively frequent event.

Currently, when that happens, I repeatedly split the list of asset IDs I request into two halves and call the API again on those two lists. This usually results in 9 to 11 requests instead of just one that would've otherwise been required.


The ContractItems API's have a similar thing going like explained in the quote, where I have to split the requests up in order to get the max details. This after you do the ContractsItems call for contractID's you just got via Contracts API...

But, what grinds me the most is the fact that a request for the corp AssetList would contain IDs that did not move, though, when you request the Locations API for those IDs (moments after receiving the IDs from the AssetList. endpoint), you'd get "135: Owner is not the owner of all itemIDs..." : \ I also have to split the assetIDs up and kinda ignore the errors though, which sucks.

Proud developer of SeAT! A Simple Eve API & Corporation Management Tool.

Project Page: https://github.com/eveseat/seat
Cor'len
Doomheim
#80 - 2014-04-20 00:05:29 UTC
As both a PI enthusiast (who need to go set up 20+ planets again and oh god the RSI) and an API dev, getting PI information exposed in the API makes me super happy!

Keep up the good work, and it'd be awesome to get a listing of how full each spaceport/etc is.