Back to blog

Google Ads API Access Levels After the Developer Token Sunset (2026 Guide)

Developer tokens were sunset on Sept 9, 2026. Here's how Google Ads API access levels now work per Cloud project: Test, Explorer, Basic and Standard.

DetectivePPC·1 day ago·8 min read

Last verified: 2026-11-19, against Google's Access levels and permissible use, Developer token and Google Ads MCP server pages.

The Brief

  • Developer tokens were sunset on September 9, 2026. API access is now granted to your Google Cloud project, not to a token or a manager account.
  • There are now four access levels: Test, a new Explorer level (production access, 2,880 operations a day), Basic (15,000 a day) and Standard (unlimited).
  • Your project is the one that owns your OAuth client (or your service account). That's the project whose access level counts.
  • Existing code keeps working, but Google says it will start rejecting developer tokens in a future major API version. Update your client libraries now.
  • If you just want an LLM or the Google Ads MCP server to read your own account, Explorer is the level to apply for, and Google says it's reviewed and approved automatically in most cases.

If you've tried to connect Claude, ChatGPT or a script to Google Ads lately and the old tutorials didn't match what you saw, this is why. The "apply for a developer token in the API Center" step is gone. Here's what replaced it, and what to check if your calls are failing.

What changed on September 9, 2026

Google moved API access management out of the API Center in your Google Ads manager account and into the Google Ads API Overview page in Google Cloud Console. Three things follow from that:

  1. You no longer need a developer token to call the API. You can still send one in the request header, but Google says it is now optional and ignored.
  2. You no longer need a manager (MCC) account to get started. You only need one if you want to link and manage multiple accounts through the API.
  3. Access levels belong to Cloud projects. If your app uses the user sign-in flow, that's the project that owns your OAuth client ID and secret. If you use a service account, it's the project that owns the service account.

The four access levels

Access levelCan accessDaily operation limitHow you get it
TestTest accounts only15,000Granted when you enable the Google Ads API
ExplorerTest and production accounts2,880 on production accounts (15,000 on test)Apply on the API Overview page; automated review and approval in most cases
BasicTest and production accounts15,000Apply after Explorer; brand verification required for new applications, then an automated review
StandardTest and production accountsUnlimitedApply after Basic; manual review, typically 10 business days

"Per day" is a sliding 24-hour window, not a calendar day. And every level is still subject to system rate limits and per-service quotas.

What Explorer can't do

Explorer is the new on-ramp. Google says 2,880 operations a day "is sufficient for most developers to get started with the API and build basic automation," and it's enough for reading and reporting on your own accounts. But it blocks a few service groups. You'll need Basic or Standard for:

  • Account creation and linking (CustomerService.CreateCustomerClient, CustomerClientLinkService, CustomerManagerLinkService)
  • User management (CustomerUserAccessInvitationService, CustomerUserAccessService)
  • Planning, including the Keyword Planner services (KeywordPlanService, KeywordPlanIdeaService and the other KeywordPlan* services), AudienceInsightsService and ReachPlanService
  • Billing and payments (PaymentsAccountService, BillingSetupService, AccountBudgetProposalService, InvoiceService)
  • Multi-party approvals (MultiPartyAuthReviewService)

That planning restriction matters if you were hoping to have an AI assistant pull keyword ideas through the API. On Explorer, it can't.

What happened to existing developer tokens

If you had an approved token before the sunset, Google looked at API call logs from the previous 90 days and gave the token's access level to every Cloud project that had used it. That leaves a few cases to check:

  • Token used with your project in those 90 days: your project inherited the same level. Confirm it on the API Overview page.
  • Token approved but never used: nothing transferred. Re-apply from your project.
  • Token inactive for 90 days: access was revoked, so the project defaults to Test.
  • New Cloud project: starts at Test, even if you hold an approved token. Old tokens can't be re-associated with new projects anymore.
  • Pending Basic application from the old API Center: closed. Re-apply in Cloud Console. Pending Standard applications were reviewed as usual.

Troubleshooting: why your production calls fail

CLOUD_PROJECT_NOT_APPROVED_FOR_PRODUCTION. In API v25 and later, this is the error for a project with Test access calling a production account (v24 and earlier return ACTION_NOT_PERMITTED). The fix is to apply for Explorer on the API Overview page.

Rejected for Explorer or Basic even after brand verification. Google lists this as a known issue. The root cause it gives is a Cloud project on the Free Trial program, or with a suspended or disabled billing account. Its workarounds: upgrade the project to a paid tier, use a different brand-verified project, or (only if nothing else runs in that project, since it turns off its other paid Cloud services) remove billing.

AUTHORIZATION_ERROR after an upgrade. Another known issue: some projects that upgraded to Explorer, Basic or Standard after September 9 aren't having the upgrade honored yet. Google says it has a fix and is rolling it out; the temporary workaround is a new Cloud project with an Explorer application.

Basic needs brand verification first. For new Basic and Standard applications, Google requires brand verification on the Cloud project. Once that's done, Google says Basic applications are automated and reviewed within minutes. Existing access holders don't have to verify, though Google encourages it.

Can't change the access level at all. You need quota management permissions on the project. Owner, Editor, Quota Administrator and Service Usage Admin include them by default.

A pre-flight checklist for AI and MCP setups

Before you point an LLM, a script or the official Google Ads MCP server at a live account:

  1. Find the right project. Which Cloud project owns the OAuth client your tool uses? That's the one to check.
  2. Confirm the level on the Google Ads API Overview page. Test means it can only see test accounts.
  3. Match the level to the job. Read-only reporting on a few accounts fits Explorer. Keyword planning, account creation or user management needs Basic or above.
  4. Update libraries. Google says it has published versions of the client libraries, the MCP server and the Google Ads API Developer Assistant that work without a developer token.
  5. Check who gets the emails. Google is moving Mandatory Service Announcements to the project's Owner and Editor users (for now it still also sends them to the API Center contact email). Make sure the right people have those roles in IAM.
  6. Keep it read-only where you can. An assistant that only needs to read shouldn't be holding credentials that can write. The official MCP server can create assets, upload videos and manage labels (with a propose-and-confirm step), and Google documents a configurable read-only mode for it.

Start your free investigation today

A scored case file for your Google Ads account in around 5 minutes.

Where DetectivePPC fits

You only need your own Cloud project and access level if you're building or running your own integration. If what you actually want is an audit and ongoing monitoring, DetectivePPC connects with read-only access and runs the checks for you.

For the manual version, start with our guide on how to audit a Google Ads account. If you're wiring an AI agent into account data, read why your AI agent needs guardrails against prompt injection too.

Verdict

PriorityActionEffort
HighConfirm every Cloud project you use shows the access level you expectLow
HighApply for Explorer on any project stuck at Test that needs production dataLow
MediumUpdate client libraries and stop sending developer tokensMedium
MediumReview IAM Owners and Editors so service announcements reach the right peopleLow
LowPlan for Basic (with brand verification) only if you need planning, account linking, user management or billing servicesMedium

FAQ

Do I still need a developer token for the Google Ads API? No. Since September 9, 2026, access is managed per Google Cloud project. Sending a token is optional and ignored, and Google says it will start rejecting developer tokens in a future major API version.

Do I need a Google Ads manager account to use the API? Not anymore. Google says you only need a manager account if you want to link to and manage multiple accounts through the API.

What is Explorer access in the Google Ads API? A level between Test and Basic. It allows up to 2,880 operations a day against production accounts, is reviewed and approved automatically in most cases, and blocks account creation and linking, user management, planning, billing and multi-party approval services.

My developer token was leaked. Should I reset it? Google says no: because access levels now live on your Cloud project, an unauthorized user can't use your old developer token with their own Cloud project.

Where do I see my access level? On the Google Ads API Overview page for your project in Google Cloud Console. That's also where you apply for a higher level.

Start your free investigation today

A scored case file for your Google Ads account in around 5 minutes.

Start your free investigation today

A scored case file for your Google Ads account in around 5 minutes.