CCP Illurkall has a new dev blog available for your viewing pleasure which details the changes coming to the API system this fall. Illurkall is the overseer of the API for the foreseeable future and will make sure it is up to snuff.

You can read all about it here

We would be delighted to receive your (constructive) feedback in this thread.

any news on Crest?

CAKs fail to encompass the abilities of its predecessor the legacy API key.

A full legacy key allows access to everything available with the account, with a CAK you are limited to 1 char, All chars or 1 Corp.

This means to equal 1 full legacy key you will need upto 4 CAKs per account. 1 CAK for all the chars and if there are 3 chars, each a director or CEO of a different corp then 1 CAK for each of them.

There is no reason for this backwards step, you can maintain the ~security~ CAKs are meant to achieve and still have an option to access ALL data for those that want it.

CAKs fail to encompass the abilities of its predecessor the legacy API key.

A full legacy key allows access to everything available with the account, with a CAK you are limited to 1 char, All chars or 1 Corp.

This means to equal 1 full legacy key you will need upto 4 CAKs per account. 1 CAK for all the chars and if there are 3 chars, each a director or CEO of a different corp then 1 CAK for each of them.

There is no reason for this backwards step, you can maintain the ~security~ CAKs are meant to achieve and still have an option to access ALL data for those that want it.

read: "Even though months and months have passed I have been too lazy to update our software; now that the plug is getting pulled I am shitting myself continuously at the prospect of having to rewrite all my code in the span of 2 weeks"

What? No pretty pictures or graphs?

Not even one showing something like....how many new keys were generated from the time they were offered?

It takes about 3 lines to make use of new keys. The reason I haven't done so is because, guess what, like I said in my first post - CAKs are not as good as a full legacy key.

your fault for writing code that relies on a goofy edge case instead of developing a proper application

fortunately for you they aren't actually shutting down old keys, just making it impossible to generate additional legacy keys, so you probably got another couple of months before you have to get off your ass and change "3 lines" of code

I did the changes 12 months ago, I simply disabled it because instead of asking for multiple keys and doing the necessary checking to make sure all have been entered I could just stick to 1 legacy key as it's just much better.

It was originally written when CAK didn't exist, so your spouting about "developing a proper application" is just stupid nonsense being spewed by a kid who just collected his Basic Computing certificate last week. Shutting down legacy API at this juncture serves no purpose other than to supply reason for a devblog. It's a system that happily runs itself and no-one is planning on adding anything to the API or working on it in any manner as all efforts are concentrated on CREST.

My only crime is that I am one of the few people who actually use all of the available API which is why hoopleheads such as yourself keep spouting rubbish about "should have updated" oblivious to the limitations that CAK pose compared to their predecessor.

Hey

I'll try to make my next DevBlog look a little bit more happy with pictures and all.
The reason for doing this is mainly an effort to keep the legacy to a minimum and making it easy for us to move forward. Because if we can move forward more freely that just means more stuff for you guys in the end.

that's an awful lot of :words: for "i'm too lazy to update my application"

also i guess you missed the locations, charactername, and contracts api stuff that they added after announcing crest

CAKs are a step backward.

Hey

I'll try to make my next DevBlog look a little bit more happy with pictures and all.
The reason for doing this is mainly an effort to keep the legacy to a minimum and making it easy for us to move forward. Because if we can move forward more freely that just means more stuff for you guys in the end.

Is this safe? Can someone steal my account?

It is safe to provide your API key to applications and web sites as long as you are prepared to allow the application or web site to see your character and corporation information. You can specify which information is accessible for each customizable API key.

Sharing an API key does NOT give people access to your account while sharing your account password would. Therein lies the whole purpose of API keys. An API key only allows the recipient to view your character and corporation data but gives them NO control over it. They are NOT able to log in to the game or post on the forums with the API information. No part of the API key information is in any way generated from your account password - there is no way to calculate your password using this information.

... http://api.eve-online.com and http://api.eveonline.com will be permanently redirected to https://api.eveonline.com ...