Google Ads API Basic Access: Step-by-Step Guide [2026]

Every morning, before I look at a single campaign by hand, a script has already checked all ten of my client accounts overnight — budget pacing, performance swings, disapproved ads, search terms worth turning into keywords or negatives. That script only exists because of one thing sitting quietly in my manager account: an approved Google Ads API developer token. Without it, I'd be logging into ten separate accounts every day just to see what changed. With it, one person can run monitoring that used to take a small team.

The developer token is the entry ticket to all of that — the API is what makes agency-grade automation possible for a single operator, whether you're pulling performance data, pushing bid changes, or feeding closed deals back into Google Ads (I wrote about that last part in the offline conversion import guide, which also runs through the API under the hood). My token currently runs at Explorer access — the level Google grants automatically — and it covers all of that nightly reporting. But the moment you ask for more, say Keyword Planner calls, you hit a wall: DEVELOPER_TOKEN_NOT_APPROVED. Full functionality means Basic Access, and that means an application and a review that officially takes up to 5 business days, with no status bar and no estimate of how much longer you'll wait.

That changed on July 7, 2026. Google launched a pilot that lets you complete brand verification on your Cloud project while your Basic Access application is pending, and get a review within hours. This guide walks through the whole path — token, application, Cloud project link, and the new verification shortcut — based on how I actually set mine up.

Prerequisites

Two things need to exist before you touch the application form. Neither costs money, and if you're already running Google Ads, you probably have the first one.

Step 1 — Get your developer token

In your manager account, open the API Center — under Admin in the current interface (older accounts may still show it under Tools & Settings). This is where the developer token lives, and where its current access level is shown. If you've never applied before, generating the token itself is instant — you don't need approval to get a token, only to use it against real accounts.

A brand new token starts at Test Account Access: it works only against test accounts you create for development and can't see a byte of production data. Google then automatically grants many accounts Explorer Access — no application needed. That's the level my token is at in the screenshot above: it works against real, production accounts, but with a cap of 2,880 operations per day and no access to planning tools (Keyword Planner), account creation, user management, or billing services.

Explorer is a perfectly usable entry ticket — my entire nightly reporting stack runs on it. It's also exactly where you'll first feel the ceiling, because any call to a service Explorer doesn't cover returns DEVELOPER_TOKEN_NOT_APPROVED. Before you apply for Basic, use this level to confirm your authentication and basic connection work: if a call fails here, the problem is your configuration, not your access level.

Step 2 — The Basic Access application

In API Center, next to the developer token, there's a link to apply for Basic Access. The form asks what you plan to do with the API — and this is the part that actually determines how smoothly the review goes.

Step 3 — Link the token to a Cloud project

For brand verification to count toward your token, Google needs to know which Cloud project belongs to which developer token. You'd expect a form or a field for this — but per the official documentation, the association happens by simply making any API call that uses your developer token together with OAuth credentials from that Cloud project. That single call ties the two together.

The details that make this painless: the call can go through either the user authentication or the service account workflow, it can target a test or a production account, and it does not matter whether the call succeeds or fails. Your token's current access level doesn't matter either. The only thing that counts is that the token and the project's credentials show up in the same request.

Step 4 — Brand verification (the July 2026 pilot)

This is the new part. On July 7, 2026, Anash P. Oommen of the Google Ads API Team announced on the Google Ads Developer Blog that developers with a pending Basic Access application can complete brand verification on their Cloud project and get reviewed "in the next few hours." Google cited "significant interest from our developer community for Google Ads API access" as the reason for building the shortcut.

Brand verification is part of the standard OAuth App verification process in Google Cloud Console and is self-service for most developers — you don't need to submit anything to a human or wait on a separate approval queue for it. It lives under the OAuth consent screen / Google Auth Platform → Branding section of your linked Cloud project.

The whole process, screen by screen

1. Open the OAuth consent screen. In Google Cloud Console, select your project, then go to APIs and services → OAuth consent screen in the left menu. That drops you into the Google Auth Platform section of the console.

2. Click Get started if the platform isn't configured yet. If you've never set up OAuth consent for this project, you'll land on an empty Overview screen with a Get started button.

3. Fill in the project configuration. Four short sections — App Information (app name and support email), Audience, Contact Information, and Finish — then click Create.

4. Switch User type to External and publishing status to In production. On the Audience tab, if User type says Internal, click Make external. Google's documentation is explicit that for this review your User type must be External and publishing status In production — even if your tool is strictly internal. Pick In production in the dialog and confirm the Push to production prompt.

5. Complete the Branding tab. This is the information users see on the consent screen: your application home page, privacy policy and terms of service links, authorized domains, and a developer contact email. Click Save.

6. Click Verify branding. The button sits in the top-right corner of the Branding tab, inside the Verification status card.

7. Wait a few minutes. Verification is automated, and the interface itself says it can take up to 5 minutes. If an error comes back, fix what it points at — usually a domain or link issue — and run it again.

8. Publish the verified branding. Once verification succeeds, click Publish branding. Don't sit on this one — the verified result expires in 7 days if you don't publish it.

9. Done: the project is brand verified. The status card now shows a green confirmation that your branding is verified and being shown to users. This is the signal Google's team sees when it picks up your pending Basic Access application.

What Basic Access gives you — and what it still doesn't

Once approved, you get the API's full feature set against every production account under your manager account, up to 15,000 operations a day. That includes exactly what Explorer excludes: planning tools (Keyword Planner calls for keyword ideas and volume), account creation, and billing services. My day-to-day stack — reporting that generates itself every morning, pacing, performance and disapproval monitoring across all accounts — already runs at Explorer level. For a solo operator watching ten client accounts, Basic's daily cap is not something you'll bump into.

Keyword Planner was the first thing that hit the ceiling for me: calls for keyword ideas and search volume returned DEVELOPER_TOKEN_NOT_APPROVED, because planning tools simply aren't part of the Explorer level. Until Basic comes through, I estimate volume from Search Console impression data plus benchmark CPCs, which is close enough for planning decisions. But if keyword research through the API matters to your workflow, Basic Access isn't optional — it's the requirement.

If you're running automation for your own agency's accounts, Basic Access is almost certainly all you'll ever need — Standard exists for tools built to serve large numbers of external advertisers at high volume, which is a different problem than one MCC and a handful of client accounts.

Frequently asked questions