Google Ads API: Access Levels, Limits and the End of Developer Tokens

Here's the catch. Test access only works on test accounts, and test accounts don't serve ads. To touch a live account you need at least Explorer, which Google approves automatically in most cases but caps at 2,880 operations a day against production accounts. The good news is you no longer need a developer token or a Google Ads manager account to get started.

The four access levels, side by side

Access level	Accounts it can reach	Daily operation limit, as of October 2026	Review
Test	Test accounts only	15,000 on test accounts	Granted when you enable the API
Explorer	Test and production	2,880 on production, 15,000 on test	Automated in most cases
Basic	Test and production	15,000 on both	Automated, within minutes of brand verification
Standard	Test and production	Unlimited on both	Manual audit, typically 10 business days

A day here isn't a calendar day. Google counts operations over a sliding 24-hour window for your Cloud project, and you get a RESOURCE_EXHAUSTED error if you go over. Google says Explorer is enough for most developers to get started and build basic automation, and Basic is enough for most developers, full stop. Standard is for large companies or tools that serve many users.

What Explorer access can't do

Explorer blocks four groups of features. If you need any of them, apply for Basic or Standard.

Restricted on Explorer	Services affected
Account creation	Creating client accounts
User management	Inviting users and managing user access
Planning	Keyword planning, audience insights and reach planning
Billing and payment	Payments accounts, billing setup, account budget proposals and invoices

How to get Google Ads API access now

1. Enable the Google Ads API in your Google Cloud project. Your project gets Test access straight away.
2. Open the Google Ads API Overview page, check your level shows as Test, expand Upgrade access level and click Apply for access. Google may upgrade you to Explorer automatically.
3. For Basic, complete brand verification for your Cloud project first, then apply the same way. Applications are reviewed within minutes of verification and submission.
4. For Standard, click Start application. Expect questions about what your tool does and who uses it, demo sign-in access if outside users use it, and a check that it meets Google's Required Minimum Functionality.
5. Reply promptly to Google's Compliance team, which emails you during the review and again with the outcome.

To manage access levels you need quota management permissions on the Cloud project. Owner, Editor, Quota Administrator and Service Usage Admin roles include them by default. You'll still want a manager account if you need to link and manage several Google Ads accounts through the API, and my guide to the Google Ads manager account covers setting one up.

What changed on 9 September 2026

If you already had an approved developer token, Google moved its access level to every Cloud project that used it in the 90 days before the sunset. Your access now comes from the project that owns your OAuth client ID and secret, or your service account. Existing code keeps working, and you can still send the token in your headers, but the servers ignore it, and Google says it'll start rejecting tokens in a future major version.

• Pending Basic applications made in the old API Center were closed. Re-apply from the Overview page.
• Pending Standard applications from the API Center are still being reviewed as usual.
• A token that was approved but never used didn't transfer. Apply for access on your project instead.
• A project you no longer use loses its access after 90 days of inactivity, with nothing for you to do.
• A leaked developer token doesn't need resetting, because it can't be used with someone else's project.
• Important notices now go to the owner and editor users on your Cloud project, so check those roles are current.

One error to know: in version 25 and later, calling a live account from a Test project returns CLOUD_PROJECT_NOT_APPROVED_FOR_PRODUCTION. Older versions return ACTION_NOT_PERMITTED instead. Either way, the fix is to apply for Explorer.

Two known issues, as of October 2026

Problem	Cause and workaround Google gives
Explorer or Basic refused even after brand verification	The project is on the Cloud Free Trial or has a suspended or disabled billing account. Upgrade to a paid tier, or apply from another brand verified project.
AUTHORIZATION_ERROR on live accounts after upgrading	Some upgrades made after 9 September aren't being honoured yet. Google has a fix rolling out; meanwhile, apply for Explorer on a new project.

How Google counts operations

Request or rule	Limit or how it counts
Search or SearchStream request	One operation, however many batches it returns
Paginated request with a valid page token	Not counted
Request rejected with a GoogleAdsFailure	Still counted
Network failure that never reaches Google	Not counted
Mutate request	No more than 10,000 operations per request
Keyword idea and forecast methods	1 request per second per account
Click or call conversion upload	2,000 conversions per request
Account budget changes	1 operation per request, and wait at least 12 hours between changes to the same account
Pending invitations	No more than 70 per client account

That 12-hour rule is the one I'd stick on the wall. Google warns that budget changes made sooner may cause failures that only your Google Ads account representative can resolve. Responses are also capped at 64 MB, so select fewer fields or use streaming on big reports.

New builds need the Data Manager API

Two older routes are closed to new adopters. Since 1 April 2026, new Customer Match integrations must use the Data Manager API instead of the user data services, and since 15 June 2026 the same applies to new click conversion uploads. Existing integrations aren't affected, but if you're starting from scratch, plan around the Data Manager API. For the tracking side, here's my guide to Google Ads conversion tracking.

Permissible use on Standard access

Standard projects also get a permissible use. Ad creation and management opens every service for building campaigns, ad groups, ads and keywords. Reporting allows read-only calls for developers who only want stats. Researching keywords and recommendations opens the recommendation and keyword planning services. You can apply to change it later, for example to give your clients access to your tool.

My verdict on the Google Ads API

For most businesses, Explorer is plenty: 2,880 operations a day on live accounts covers reporting and basic automation, and approval is usually automatic. Apply for Basic only when you hit a restricted feature such as keyword planning or user management, and leave Standard to software companies. The bigger shift is that the API now opens straight from Cloud console, with an MCP server for AI assistants, so automating Google Ads reporting is simpler to start than it used to be.

Wiring Google Ads into your own reports or an AI assistant is a good automation project, and it's the kind of thing I help teams plan. I run AI training and workshops for teams, and help businesses with AI enablement, AI automation and GEO, which is about getting your business seen and cited in AI answers. Most of that work is with SaaS marketing teams and small businesses. Here's how we can work together.

Frequently asked questions

Do I still need a developer token for the Google Ads API?

No. Developer tokens were sunset on 9 September 2026. Access levels are now managed on your Google Cloud project, and tokens sent in requests are ignored.

How many operations a day does Google Ads API Explorer access allow?

Up to 2,880 operations a day against production accounts and 15,000 a day against test accounts, counted over a sliding 24-hour period.

Do I need a Google Ads manager account to use the API?

Not anymore. You need a manager account only if you want to link and manage multiple accounts through the API.

How long does Google Ads API Standard access take?

Google says Standard access reviews typically take 10 business days, and they involve a detailed manual audit of your tool.

Why do I get CLOUD_PROJECT_NOT_APPROVED_FOR_PRODUCTION?

Your Cloud project only has Test access and you're calling a live account. Apply for Explorer access on the Google Ads API Overview page.