Last November Google launched a new API console to help developers manage the Google APIs they use in applications and websites. When launched, the API console provided tools for managing 8 of Google APIs, including traffic controls, an API limit list, and a form for requesting more usage. The console also provided reports, with a graph for each activated API showing a breakdown of requests. During Google I/O 2011, Google quietly released some enhancements to the API console.
The enhancements were announced in the Life of a Google API Developer session (video embedded below):
Enhancements to the traffic controls include limiting requests from specific domains, establishing usage limits and setting request limits on a per-user basis.
With the new granular API traffic controls, some APIs in the console also allow for billed usage. There are currently three APIs that allow billable access:
Each of these APIs has its own pricing and is integrated with Google Checkout for billing, with invoicing for API usage each month. Billable limits can be configured using the traffic controls, keeping costs under control.
In the updated console, API access has been upgraded to support the issuing of OAuth 2.0 tokens which Google has evolved all APIs to support.
The API Console now lets developers manage access keys, view usage with traffic reports, manage traffic, and pay for usage for up to 15 separate Google APIs.