EVE Technology Lab

There is some documentation here: https://neweden-dev.com/Category:CREST

It's not very complete due to... well me being a lazy ... something. You can get that same documentation though from us. Say you want the documentation for the new system costs. And maybe you don't know how to find where the system cost resource is located. The following is how you would go about it:

• Go to https://public-crest.eveonline.com/ As CREST is a RESTful API everything should be linked from the root in some way. So you can always explore the links in the root to see what exists. Note however that many of the links in the root will return 404 (I think it's 404) as we have not exposed them on public CREST yet. Public CREST is a bit of a hack.
• After browsing through the links from the public CREST root and finding a resource you want more information about simply take that same resource and do an OPTIONS call on it from CREST instead of public CREST.
• Example: You want details on https://public-crest.eveonline.com/wars/ resource. Instead of doing a GET request do an OPTIONS request and do it on https://crest-tq.eveonline.com/wars/ and from that you will get complete documentation of the resource. This OPTIONS call is applicable to all resources. Even if you don't have access to them.
• The above is how the documentation on NewEden-Dev was being grabbed.
• Enjoy!

With new feature "pay to another character playing time" by Plex - I want know who I bought it and see it in transactions.

Is it possible to determine through the API in transactions or journal who was paid for playing time with Plex?

Here's a handy way to explore the CREST API http://jimpurbrick.com/crestexplorerjs/#https://public-crest.eveonline.com/ which also makes a useful example JavaScript client. The code is here https://github.com/jimpurbrick/crestexplorerjs .

Oh, you're generating the documentation from OPTIONS (sorry I finally read your post properly, finally).

So, people can generate their own documentation from the API to some extent: neat!

We are deploying a few minor changes to the XML API today during downtime, nothing drastic just a few minor changes that were brought to our attention as something that should be fixed.

Fixing the columns!
The XML API has this concept of rowsets and rows. Each rowset has an attribute for columns which each row has. Depending how you implement your parsing of the data returned by the API you may or may not care about the columns. If you do care about the columns attribute you usually care about the order the columns are listed in along with spacing of the information. While we attempt to test the API as much as possible before deploying it to TQ, none of us (that I am aware of anyways) use the columns data and we often forget how important it is to you guys. So this morning I sat down and fixed a few instances where this was broken.

• The corp/MemerSecurity endpoint had a space between characterID and name in the members rowset. This has been fixed.
• The eve/CharacterAffiliations endpoint had the columns in completely the wrong order and this has been changed to match how the data is actually returned.

These fixes are very quick and easy for us, so if you are aware of any other problems with column data please let us know. Also feel free to politely remind us when we release changes that break this of how important it is to you.

ContactList and the WatchList
The char/ContactList endpoint now returns an attribute called “inWatchlist“ for each contact in the contactList rowset (and yes, we added the attribute to the column information in the correct order). This is a simple Boolean value that should let you figure out which of your contacts are on your watch list or not. Someone asked for this and it was easy, not really sure how you will use this but since it was so easy why not! :D

Example output: http://pastebin.com/NYQjXZ1i

As I said at the beginning of the post, nothing crazy just a few minor changes to help improve the life of third party developers.

Is it possible to get a fix for the IndustryJobs API returning "0" and "" for the productTypeID and productTypeName attributes?

Ta very much.

This is probably not the answer you want to hear, but I will be looking into that hopefully the week after next. I know it's a pretty high priority thing to fix, but we have some other stuff in the works that I need to get done first. :)

I've searched for this a number of times but can't find the answer so please excuse me if it's a duplicate and point me to the thread or resource.

I'm having problems with the PlanetaryPins API. What do I need to do trigger a refresh in the data? I've tried keeping the planet open in Planet Mode and clicking on each facility to open them up. Still the data is stale. I don't mind jumping through hoops to get refresh the data but at this point I'd be better off manually inputting the data... and I hate data entry.

The Corporations resource has not been exposed publicly yet.

Unfortunately, not all the endpoints are exposed (or even created.)

It's just easier to have them pointing like that on the existing ones, so you don't have to go back and change everything which points at them when they go live.