AdWords API

Signing up for the AdWords API

To use the AdWords API, you must request and be granted access as described below.

signup flow

Step 1: Select a suitable MCC account

You need to have a My Client Center (MCC) account to apply for access to the API. If you do not already have an MCC account, you will have to create one. MCC accounts cannot be created using the same email address as an existing AdWords account. You therefore need to use an email address that has not already been associated with an AdWords account to create your MCC account.

Note that the MCC account you select has no effect on the set of AdWords accounts that your API token can access. However, linking this MCC account to your company's active AdWords accounts will streamline the application review process and reduce the number of times you need to go through the authentication process to manage your accounts via the API. For details, see these instructions for linking accounts.

Step 2a: Apply for access to the AdWords API in your MCC account

You can sign up for the AdWords API when logged in to your MCC account. Navigate to [Settings (gear icon in top right corner) > Account Settings (drop-down menu) > AdWords API Center (left menu)] and follow the instructions to apply for AdWords API access.

Make sure your information is correct and your company's website URL is functioning. If the website is not a live page, we will not be able to process your application.

Make sure the developer contact information you provide leads to a regularly monitored inbox. If we cannot contact you via this email address, we will not be able to process your application and it will be rejected. You can edit your contact email in your MCC account Preferences [Settings (gear icon in top right corner) > Account Settings].

We strongly encourage you to keep this information up to date even beyond the application process to allow us to send you important service announcements.

In order to ensure that the tool or software application you propose to use with the AdWords API is in compliance with our Terms and Conditions (T&C) and Required Minimum Functionality (RMF) (if applicable), we will contact you shortly after you submit your application to request additional information (see Step 2b below). If your company manages AdWords accounts for clients, please note that you must be in compliance with our Third Party Policy to gain access to the AdWords API.

We currently estimate that we will initially contact you within one week of the date you submitted your application. In the meantime, you can try out the API with test accounts.

Step 2b: Continue your application

After completing Step 2a, a link to a follow-up application form will be sent from adwordsapi-tokens@google.com to the email address listed in the AdWords API Center. Please complete this follow-up form to continue your application.

If you no longer have access to this inbox, or if you are not planning to actively monitor this email address, please edit your email address in the AdWords API Center by following the instructions above in Step 2a, so we can contact you. Then (re)submit the follow-up application form and we will get back to you within 2 business days.

Step 3: Set up billing and accept Terms and Conditions of usage

Make sure you have provided billing information in your MCC account by navigating to [Settings (gear icon in top right corner) > Billing Preferences]—you will need a credit card at this step. You will be prompted (on the last screen of the billing setup wizard) to accept the AdWords API Terms and Conditions. The Terms and Conditions must be accepted in order for your API requests to succeed. If you already have invoice billing set up, please contact your CSR or Account Manager and they can help you accept the Terms and Conditions.

Step 4a: Token Review team has approved my Developer Token

Your assigned Developer Token will be activated once your application for API access is approved. Your token will be available through your AdWords API Center—accessible through the My Account menu for the MCC account from which you applied. You'll be able to access the API by including it in your request headers when interacting with our system.

It is very important that you keep your Contact Email up-to-date—we may send you important information regarding disruptions to service and urgent changes via this channel.

If you make any changes to your tool in the future, you must report these changes to Google as per the AdWords API Terms and Conditions section II-5. You may report these changes by filling out this form.

Step 4b: Token Review team has rejected my application

The Token Review team examines the information you have provided when you apply for access to the AdWords API to make sure that your software adheres to the AdWords API Terms and Conditions (T&C) as well as the Required Minimum Functionality (RMF) (if applicable).

Common reasons to be rejected include:

  • We cannot reach you at your developer contact email address.
  • You have applied because a tool you use from a third party requires a developer token.
  • Your application violates other provisions in the T&C.
  • Your application does not implement required elements of the RMF (if applicable).

If you have altered your API tool to adhere to AdWords API policy or if you believe your application was incorrectly rejected, you can re-apply by clicking the "Reapply" link in the AdWords API Center page of your MCC account.

Next steps

If you have not received an email from us about your application within the expected amount of time, follow these steps. If you have any further questions, please fill out this form.

After you've signed up with the AdWords API, download a client library and browse through the Developer's Guide. If you have questions regarding the functionality of the AdWords API, post on the developer forum.

To receive important updates, subscribe to the AdWords API Announcements group, Google+ page, and AdWords API blog. The blog is our primary channel of communication regarding changes and updates to the AdWords API and we strongly encourage you to read it regularly.

Authentication required

You need to be signed in with Google+ to do that.

Signing you in...

Google Developers needs your permission to do that.