Reminder: Accept your AdWords T&Cs by Nov 27

Wednesday, November 15, 2006

Just a reminder about our September 5 post... please make sure that you and/or your clients accept the new AdWords Terms and Conditions for each account that you manage via the API by November 27. Failure to do so may result in access to these accounts being blocked after the 11/27 deadline.

If you have the authority to accept the terms and conditions for all of the AdWords accounts under your MCC, please see the Sept 5 post for instructions on how to “batch accept” the AdWords Terms and Conditions.

NOTE: These Terms and Conditions apply to AdWords account owners (regardless of whether or not they use the API), and are separate and distinct from the recent changes announced to the AdWords API beta Terms and Conditions.

-- Jon Diorio, Product Marketing

BUG: October 29 Stats Retrieval

Tuesday, November 14, 2006

Thanks to those of you who pointed out the issue surrounding stats retrieval for October 29, 2006.

Attempts to retrieve stats for 10/29/2006 – 10/29/2006 will return an empty/null set. This affects all stats methods. However, any request that includes a broader date range that includes October 29 should return accurate data (including the data for October 29).

If you need specific stats for October 29, request stats for October 28 and for Oct 28-29, and then take the difference between them.

We are working to resolve this issue now and will have more information as soon as it has been corrected. Thank you for your patience.

-- Jon Diorio, Product Marketing

Fixed: API Latency Bug

Tuesday, November 14, 2006

We apologize for the delay. On November 4 we identified and corrected the API latency bug that we reported on November 3. Since then, system response times have returned to their normal levels.

We apologize for any inconvenience that this may have caused you.

-- Jon Diorio, Product Marketing

API Version 7 Now Available

Thursday, November 09, 2006

We are happy to announce the release of the AdWords API Version 7 (V7).

V7 introduces three major changes to the AdWords API. This announcement highlights only the major components of the release. For complete details on all V7 changes, please see our Release Notes.

V7 Highlights

    Cross-Ad Group Criteria Updates: Update keywords in multiple ad groups with a single API call

    Ad Scheduling: Enable the ad scheduling advanced bidding feature

    Pausing/Resuming of Keywords, Sites and Creatives: Pause/resume any keywords, creatives or sites (Sandbox-only feature)

Pause/Resume Keywords, Creatives and Sites

    Based on developer feedback, we are releasing this feature in the AdWords API Sandbox prior to its availability in the API and the AdWords website. The official API and web application launch is scheduled for mid January.

V6 Sunset in March 2007

    In order to avoid requiring code changes during the busy holiday season, we are extending the standard two month sunset period to approximately four months. Therefore, V6 will be turned off on March 12, 2007. Please make sure that you upgrade to V7 before this date.

    And as a reminder, please remember that we will be shutting down V5 on January 24, 2007.

As with every new version, we strongly urge you to review the Release Notes section of the Developer’s Guide.

-- Jon Diorio, Product Marketing

System Maintenance - November 11

Tuesday, November 07, 2006

We will be performing routine AdWords system maintenance from 10 a.m. to 2 p.m. PDT on Saturday, November 11, 2006. While all AdWords advertisements will continue to run as normal, you may not be able to perform API operations during this maintenance period.

--Jon Diorio, Product Marketing

Tips for Handling Error 129

Friday, November 03, 2006

It seems that some of you have recently encountered Error 129 (“You can't use the API until you complete the signup process and are approved”).

If you encounter this error, please check the following:

  • Have you completed the API registration process? If you have not completed the process, you should see warning messages on the AdWords API Center prompting you to complete the necessary steps.
  • Did you update your request header to incorporate the new developerToken and applicationToken arguments? And are the proper tokens entered for each?
  • Have both your Developer Token and Application Token been approved? You can check this from the AdWords API Center.
If you answer ‘yes’ to all of these questions, and are still encountering error 129, then please send an example of your SOAP request and response for which you get this error to Please keep the other headers intact in the Request XML and replace your password with "xxx". If you need help, the sample code section of the AdWords API site shows you how to get these SOAP traces in various languages.

-- Jon Diorio, Product Marketing

Known Issues: API Latency & AdWords API Center Mislabeling

Friday, November 03, 2006

Thank you all for your feedback. We want to confirm two bugs that we have identified in yesterday’s build.

The first is causing an increase in overall API response times. The second may be causing the wrong API quota labels to appear on the AdWords API Center. We are working on fixes now and hope to have both of these issues resolved shortly.

We will update you again when these issues have been addressed. And thank you for your patience.

-- Jon Diorio, Product Marketing

API Changes Take Effect Today

Wednesday, November 01, 2006

As we first announced on April 11, 2006, today marks the start of the new AdWords API Beta program terms and conditions. Starting today, the current developer quota limits have been abandoned and developers will begin to accrue charges at the rate of $0.25/1000 quota units consumed (or local currency equivalent). We believe these changes will result in more flexible and scalable system for quota allocation and consumption.

You can find more information on the billing process at

If you are having difficulty accessing the AdWords API, please verify that you have completed your registration and have incorporated your approved Developer Token and Application Token into your API request headers.

-- Rohit Dhawan, Product Manager