Introducing the API Usage Report

Updated Feb 13, 2006:

Have you been wondering how many API calls you've been making? How about your progress on your schema migration? Or which calls you're not making at the minimum compatibility level?

The new API Usage Report allows you to view your API calls by production application, and displays the number of successful API calls, API calls failed, and API calls not at the minimum recommended compatibility level.

You can also monitor the progress of your schema migration efforts, tracking which calls you've made using the legacy XML API versus the unified schema.

Please Note: Although the report will store up to 6 months of data from today's date, special data tables were created for this report and the earliest data available is from January 28, 2006.

Read more about the new API Usage Report in the Product Roadmap.

Feb 13, 2006 update for REST Developers:

REST API Developer Impact:

We have found a bug in the API Usage Report where REST API developers using unified schema will incorrectly be informed that their calls are still "legacy". We are working on a fix for this now and anticipate the fix to be released by end of Feb 2006 for US and mid March 2006 for international.

REST API developers who are still using the legacy REST API can update the REST output to unfied schema by passing "Schema=1" in the query string of their REST call and modifying the application to handle the new output. For more information on using unified schema in REST, see our REST API Documentation.

Authentication Token Tool

For developers using the Authentication Token Tool , you will have 2 calls displayed on the API Usage report as legacy calls: SetReturnURL and GetUser for each token generated by the Tool. We are scheduled to migrate the API used by Authentication Token Tool by May 2006.