This checklist will take you through the process to get started with the
Google Ads API. The steps are divided into several categories, some of which you might
decide to skip if they aren't applicable to your needs. To get the most from
this document, read and execute steps in order.
The list contains three types of items:
Todo: Steps that are required in order to perform a certain
or set up a certain part of your tool.
If you're printing the checklist, you can use the checkboxes on the left to
mark which steps are completed. This checklist provides a recommended reading
order for the information found in the Google Ads API docs.
Access and setup
If you're not sure what to use the Google Ads API for and are interested in
use cases and ideas, start by watching
our introductory video.
Sign up for access
Obtain your developer
token from the API Center of your top-level manager account. All
fields on the API Access form must be completed, and the Terms and Conditions
accepted. Make sure the API contact email you provide leads to a
regularly monitored inbox. You will be issued a developer token with the
test account access
To get your token approved for production access, you'll need to fill out our
follow-up application form
and explain how you intend to use the API. You'll also need to provide a design
document. You can use
template to get started. Please provide as much detail as possible. Our
token review team will contact you if they need more information, but you can
also reach out to the email alias firstname.lastname@example.org
if there is no feedback within 2 business days.
Set up a client library
We use OAuth 2.0 for authenticating your requests against the API.
Please follow the instructions in our
OAuth 2.0 guide to set up the credentials
for OAuth 2.0. For troubleshooting, you can use the OAuth 2.0 playground.
We provide client libraries for some
common programming languages. Download the library for the language you want to
Read the blog post
Announcing Google Ads API Doctor. The tool verifies the configuration of
your OAuth2 credentials, and guides you through fixing any OAuth2 problems it
detects in your client library.
Google Ads Doctor from
GitHub, set it up, and run it to verify your Google Ads client OAuth2
Developer Token - Access Levels
Read about Access Levels, and decide
whether your tool will require more than 15,000 operations per
day at some point in the future. If it will, you will need to apply for
Standard Access for
unlimited mutate operations and
GoogleAdsService.Search requests per day. However, this is still
subject to the daily limit of 1,000 get operations.
Review the Rate Sheet to
understand how operations are calculated for your access level. Note,
GoogleAdsService.Search requests with the page_token
field set does not count towards the operations limit.
Take a quick overview
of reporting, and an
example to summarize the
performance of an account over the last 30 days using
as the single source of truth for reporting in Google Ads reporting.
Get a service account key
if your application just needs access to your own Merchant Center account. But
if you’re writing a third-party application that needs access to your clients’
Merchant Center accounts, review the
guide with OAuth 2.0.