Google Ads API removes developer token: what changes?<\/h2>
Google sunset the developer token on September 9, 2026. Previously, the 22-character token was the key point associated with API permissions. After the change, access levels are determined by the Google Cloud Project behind the OAuth client ID\/secret or service account used by the application.<\/p>
The old token may still remain in the request header, but Google servers will ignore it. Existing applications can therefore continue operating without immediate changes. However, Google recommends updating libraries and gradually removing the developer token field; a major API version in the future may reject tokens sent along with requests.<\/p>
Not all permissions are automatically the same<\/h3>
For existing developers, Google transfers active permission levels to Cloud Projects that called the API using the corresponding token within the 90 days before the sunset date. New projects, low-activity projects, or projects that have never been used may only have Test access. Therefore, the important question is no longer \"do I still have my token?\" but rather \"does the correct project used by the application have the required access level?\"<\/p>
![\"Google](\"https:\/\/dps.media\/wp-content\/uploads\/2026\/10\/google_ads_api_bo_developer_to_img2_1791781789460.png\" "\\"\\"")
<\/p>
Do old systems need to be fixed immediately?<\/h2>
Usually not yet. If the application is running stably, requests can still send old tokens and Google will continue processing them. There is no need to replace all production configurations serving campaigns just because of a sunset notice.<\/p>
However, \u201cno need to fix yet\u201d does not mean \u201ccan be ignored\u201d. When changing servers, creating new OAuth credentials, migrating projects, or upgrading library versions, permission configurations may differ. A report synchronization job may still run on the old project, while a new feature uses a new project that only has Test access. The error often only appears when calling production accounts.<\/p>
- \n
- Record the Cloud Project that owns the OAuth client ID\/secret or service account of the application.<\/li>\n
- Open Google Ads API Overview in Google Cloud Console and check the access level of the correct project.<\/li>\n
- Confirm the target Google Ads account, OAuth users, and IAM permissions for managing the project.<\/li>\n
- If the application uses Google Ads libraries, review the changelog and schedule a version upgrade to remove developer token declarations when appropriate.<\/li>\n
- Test in a controlled environment before updating workflows that are spending real budget.<\/li>\n<\/ul>
Where to register or upgrade permissions?<\/h2>
Developers now register Google Ads API access through Google Cloud Console, on the Google Ads API overview page of the project. The process for requesting or upgrading access levels in the API Center of the Google Ads manager account has been moved; API Center is now mainly used to review information about existing developers.<\/p>
Test, Explorer, Basic, or Standard access levels still have their own limits and processes. Choosing an access level must match the intended usage and Google Ads API policies. For some levels such as Basic or Standard, Google may require verification of the project's brand. Administrators should also update owners\/editors and contact emails in IAM to receive policy notifications.<\/p>
Do not confuse API access with advertising budget. Budget determines campaign spending limits; API access determines whether an application can call allowed functions. To automatically create or edit campaigns, the system must also pass OAuth, have appropriate Ads account permissions, comply with policies, and be checked before execution.<\/p>
How far can Claude, Antigravity and Codex support vibeads?<\/h2>
Programming assistants can help write connectors, query reports, build campaign drafts, or create data validation workflows. When connecting to Google Ads API, they still need a properly configured integration layer: OAuth credentials, a Cloud Project with suitable permissions, the correct customer account, and limited operation scopes.<\/p>
For small teams, a safe experiment can start with read-only reports: retrieving costs, conversions, and ad statuses, then asking the person in charge to compare them with the Google Ads interface. When moving to campaign creation or editing, add human approval steps, daily budget limits, and operation logs. Do not put access keys into prompts or public code repositories.<\/p>
In short: vibecoding reduces the effort required to build tools, but it does not remove Ads management responsibilities. An AI can suggest bids; operators still need to check goals, tracking, landing pages, and allowed spending levels.<\/p>
![\"Google](\"https:\/\/dps.media\/wp-content\/uploads\/2026\/10\/google_ads_api_bo_developer_to_img3_1791782335813.png\" "\\"\\"")
<\/p>What does DPS.MEDIA recommend marketing teams prepare?<\/h2>
Start with a small inventory checklist: which applications are calling the API, which Cloud Project each application uses, what access level is currently assigned, and who is responsible for IAM. Then separate testing from the production environment so changing credentials or upgrading libraries does not interrupt reporting.<\/p>
If you are trying Claude, Antigravity, or Codex, clearly describe the tool's scope: reading reports, suggesting content, or being allowed to submit changes to the account. Least-privilege access and approval processes remain more important than the speed of generating code.<\/p>
Google Ads API is moving from a model centered around developer tokens to permissions linked with Cloud Projects. Old systems may continue running, but projects, access levels, and libraries should be reviewed before the next upgrade or integration expansion. See the guide officially about Google Ads API developer token changes<\/a> to compare with the latest process.<\/p>