We're working on a new version of the Pivotal Tracker developer API, with a long list of improvements. The release of this is a few months away, but to prepare for it, we're removing the old version (V2) of the API. This change (removal of V2) is tentatively planned for January 27, 2012, just over three weeks from today.
If you're using the API, please make sure that you're using the current version (V3), as requests to V2 will no longer work.
To see which version you're using, look at the URLs of the requests you're sending. If you see "v2" in the path, for example /services/v2/projects, you're using the old version, and will need to upgrade to the current API version.
If you have any questions, or could use help figuring out how to make your code work with the V3 version of the API, please send an email to tracker@pivotallabs.com.
Apigee, a company that helps you use and develop APIs, just announced a number of new API consoles, including for Pivotal Tracker. The Pivotal Tracker API Console allows you to explore the API from within your browser, and makes it easy to test and debug your code that uses the API. Check it out!
For the rest of the new consoles, see the Apigee announcement blog post.
We've added a new email notification to Pivotal Tracker which will let you know when someone assigns a story to you. There are also a few new additions to the API, related to projects and iterations.
We're planning a Pivotal Tracker upgrade on Jan 23. As part of this release, we will be introducing a new API version (V3), which will make it easier to follow project activity, allow you to add file attachments, move (re-prioritize) stories, associate source commits with stories, and more.
The current API version (V2) will not change, but V1 will no longer work. If you're still using V1, you will need to change your client code to use V2 or V3.
To find out what's changing in V3, continue reading.