A couple of bugs have been reported at the Google AdWords API blog, and web developers using the API should be on the lookout for these issues.
One bug affects the API registration process, as described by Diorio:
(The bug) is preventing some developers from successfully entering their billing information and accepting/rejecting the Terms and Conditions. We have identified the issue and hope to have a fix in place in the next few days.
Please note that this bug only affects the “billing information” stage of the registration process. Therefore, all users are still able to complete the “developer and application information” stage of the process.
In the meantime, if you need to review the new Terms and Conditions, you can find a temporary copy available at http://www.google.com/apis/adwords/terms_preview.html.
The other bug Diorio discussed affects the API Sandbox:
we identified a bug in the AdWords API sandbox that results in requests returning error code 131. We are working on a fix now. In the meantime, we would like to recommend a work-around.
Developers can still work with the sandbox by using the older V4 request headers. Specifically, developers should use “token” instead of “developerToken,” and they should not include “applicationToken” in their headers.
Google makes the API available to assist developers in their construction of applications that can interact directly with the AdWords platform. Developers can build applications to generate custom reports, integrate AdWords data with other databases, and otherwise manage accounts, according to Google’s API homepage.
—
Tag:
Add to 
Bookmark murdok: 
David Utter is a staff writer for murdok covering technology and business.
