I’ve just read the details of the new Eve dev blog concerning the Tyrannis API “improvements” and I have to say, I’m pretty disappointed by what I’ve read.

The two major additions to the API include details of Contacts and of the new Calendar, with both these systems available immediately as part of EveGate. My main gripe with this is that the API is read-only and yet we are also being given more access to these via the website. Does that make the API pointless? Well, there may be some mileage in trying to integrate the calendar appointments into an existing digital calendar but even then, the system is still read-only. But realistically, if I want to view contact and calendar information out of game, I’ll just end up visiting EveGate.

Personally, I would have much rather the development time on the API been focussed on coming up with solutions to other more critical APIs than on something with is virtually overshadowed by another out-of-game system. The Mail API needs drastic improvements, and we desperately need a Blueprints API and a Contracts API. Hell, they could have even provided us with PI-specific APIs for keeping track of our new Command Centres! But it appears that CCP just doesn’t listen to third-party developers and they just code whatever they like and hope it satisfies us.

In addition, CCPs decision to make the Contacts available via the limited API key is a bad one. I do find it laughable that people are spouting privacy concerns in a game but semantics aside, I agree that this information should only be made available using the full API key. Anyone in possession of my limited API key cannot view my transaction history or my current market orders, so why would they get to see my address book? This seriously needs changing and hopefully, it’s just a quick amendment for CCP to implement.**

On a slightly good note, there are a couple of new APIs dealing with Outposts so corporations with a large amount of these can keep track of their locations, services and settings. The POS API also gets a modification to take account of the new standings settings that can be applied.

So, how does all this affect EveHQ? Well, not a great deal actually. As usual, I will be providing support for all the new APIs insofar as the API Checker and API Relay sections. Other than that, I can only envisage the POS Manager getting a slight upgrade to take account of the new settings.

Let us hope the winter patch brings us better fortunes in the API department.

** Edit: A victory for common sense! CCP Prism X now reports that the Contacts API will require the full key