EVE Technology Lab

Could we get an API (or CREST) endpoint for Bookmarks?

They have been changed to server-side storage not long ago, and just recently I discovered the usefulness of the "Notes" field.
Ingame you have to open each note seperately, with an API endpoint you could have it a bit more accessible.
It would also make it easier to keep track of larger bookmark sets / libraries.
Mapping software could show them on the map. Want to see how well you have covered Curse? Maybe Dotlan would provide a per-system count of bookmarks as info layer in the region map for logged-in users.

Useful data would be:
Name, Type, SystemId, System name, Creation date, CreatorId, Creator name, Notes

Are folders stored client-side or on the server? If the later, include the folder name aswell.

Awesome, thanks for the quick reply :)

If game design thinks its okay, you could even expose the coordinates.
You don't get them as numbers in the game but you see them on the map (and in space after Phoebe) - which would be consistent with celestial objects of which we get the coordinates via the SDE.
Combining those two sets of data would allow you to figure out distances between bookmarks and celestials, similar to how we can currently figure out distances between gates, stations etc.

I am sorry, I meant the following - is there a way to get costIndexes activities in the particular system other than to get a list of all systems and then search in them in my application ?

Not from CCP.

https://forums.eveonline.com/default.aspx?g=posts&t=362405 may be of interest.

FoxFour I would like to request the following read/write crest endpoints:

PUT corp/shares
GET corp/shares

PUT corp/shareholderVote
GET corp/shareholderVote

Why does each `item` under `/alliances/` have a top level `href` property?

I would access the details URI like:
response.items[0].href.href

and I would access the name like:
response.items[0].href.name

First few lines of the response (via curl -vX GET http://public-crest.eveonline.com/alliances/ )

{
"totalCount_str": "3072",
"pageCount": 13,
"items": [
{
"href": {
"id_str": "99000006",
"shortName": "666",
"href": "http://public-crest.eveonline.com/alliances/99000006/",
"id": 99000006,
"name": "Everto Rex Regis"
}
},
{
"href": {
"id_str": "99000008",
"shortName": "PILS.",
"href": "http://public-crest.eveonline.com/alliances/99000008/",
"id": 99000008,
"name": "People in Lousy Ships"
}
},

It doesn't have to be HTTP.

You can register an URL scheme and then set the callback to yourapp://whatever

Here is a Windows Phone 8.1 example: https://bitbucket.org/Fezzik/eve-sso/overview

Fairly obvious motives and may have been suggested but hopefully these are considered generally useful...

============================================
Idea: Ability to read/write corp fittings through CREST
Description: Endpoints for listing and CRUD of corporation and personal fittings. The benefit would be the ability to synchronise and update corporate fittings in game from an OOG resource.

Idea: Ability to fit a ship through CREST using charID and shipDNA
Description: Endpoint that accepts DNA or similar to fit modes to the current active ship for a given charID. The use case for this would be to fit a ship from an external resource without needing to first import the fitting to perrsonal/corp fittings. At present in order to get an externally listed fitting into game it must be copy-pasted or opened via DNA link and saved to personal fittings. Removing this step would provide a more steam-lined experience from OOG fittings a fitted ship IG.

Idea: Ability to read fleet members and composition for given charID
Description: Endpoint that lists names, and charIDs, and possibly ship information if a character is fleet boss for a given charID. Time in fleet etc also useful. Benefits would be to allow fleet tracking and reporting without the need to use the IGB. Some corporations and alliances provide loot and other payouts based on fleet participation. If there was an easy way to report on this via CREST it would remove the clunky IGB hooks that are currently required.
============================================