You no longer need one. Google sunset developer tokens on September 9, 2026, and API access now belongs to your Google Cloud project: enable the Google Ads API to get Test access, then apply for Explorer access on the Google Ads API Overview page in Cloud Console. A manager account is no longer required.
Until September 2026, you applied for a 22-character developer token in the API Center of a Google Ads manager account. Google has moved API access to Google Cloud. Applications started in the API Center are no longer processed, and Google says that page will be removed. The one exception Google names is the App Conversion Tracking API, which still uses a developer token from the API Center.
How do you get API access now?
- Create or choose a project in the Google Cloud console.
- Enable the Google Ads API in that project. This grants Test access: test accounts only, up to 15,000 operations per day.
- Open the Google Ads API Overview page in Cloud Console, expand Upgrade access level and apply for Explorer. Google reviews this automatically and approves it in most cases.
- Set up credentials. Google's quickstart uses a service account with a JSON key, and you give that service account access to your Google Ads account.
You don't need a manager account unless you want to manage several accounts through the API.
As of November 2026, Google lists a known issue: some Explorer and Basic applications are rejected when the Cloud project is on the Google Cloud free trial or has a suspended or disabled billing account. One of Google's workarounds is upgrading the project to a paid tier.
What do the access levels allow?
| Level | Accounts | Operations per day | How you get it |
|---|---|---|---|
| Test | Test accounts only | 15,000 | Enable the API |
| Explorer | Test and production | 2,880 on production, 15,000 on test | Automated application |
| Basic | Test and production | 15,000 | Brand verification, then automated application |
| Standard | Test and production | Unlimited | Manual audit, typically 10 business days |
Explorer blocks some features: creating accounts, managing users, planning services such as keyword ideas and reach planning, and billing. If you need those, apply for Basic. Basic needs brand verification of your Cloud project first, which you do on the Branding tab of the OAuth consent screen.
What if you already have a token?
- Your token's access level was copied to every Cloud project that used it in the 90 days before September 9, 2026.
- Your existing code keeps working. Sending the token is now optional and ignored, but Google plans to reject tokens in a future major API version, so update your client libraries.
- If a project didn't inherit the access level, apply for it again on that project's Google Ads API Overview page.
My advice: if you only want to automate or report on your own account, check whether Google Ads scripts are enough before you build on the API. Scripts run inside Google Ads, with no servers or developer credentials to manage. See which Google Ads scripts are worth using. If your goal is to let an AI assistant read your account, see how to connect Gemini to Google Ads.
Sources
- Google Ads API docs: Developer token - https://developers.google.com/google-ads/api/docs/api-policy/developer-token
- Google Ads API docs: Access levels and permissible use - https://developers.google.com/google-ads/api/docs/api-policy/access-levels
- Google Ads API docs: Quick start - https://developers.google.com/google-ads/api/docs/get-started/make-first-call
- Google Ads API docs: Brand verification - https://developers.google.com/google-ads/api/docs/api-policy/brand-verification
- Google Ads Scripts docs: Product overview - https://developers.google.com/google-ads/scripts/docs/start
