Google has set a December 7 deadline for developers who manage Google Ads accounts through its API. From the week of December 7, 2026, the Google Ads API will change how it handles multi-party approvals, the security step that asks a second administrator to approve sensitive account changes. Invitations to new users will no longer be created until that approval lands, stale approval requests will get their own error code, and up to 100 pending reviews can be cleared in a single call. Google announced the changes on November 4 and told developers using multi-party approvals to update their code before the deadline.
What changes on December 7
First, user invitations change. Today, the method creates the invitation and returns its resource name, but sends nothing until approval is granted. From December 7, the method will defer creating the invitation until the approval request is approved, and the resource name field will come back empty. Once the review clears, the invitation becomes available from the review results.
Second, stale requests get a name of their own. Google will return a new MultiPartyAuthReviewError.STALE_MULTI_PARTY_AUTH_REQUEST error code when a pending approval is no longer valid because its target was modified or deleted after the review was created. The code arrives in v26.2; versions v23 to v25 will return a generic unknown error, with the new code in a secondary field.
The third change is about volume. Developers will be able to resolve up to 100 pending multi-party approval reviews in a single call, up from one review per call today. That is a hundredfold increase, and it matters most to agencies and platforms processing access changes in bulk, such as onboarding a team across many client accounts.
Who has to act
The instruction is conditional, but the audience is clear. Any integration that invites users, changes their access or removes them through the API needs to handle the new behaviour. Code that stores the returned resource name to track or cancel an invitation will receive an empty field whenever approval is required.
Code treating an empty value as a failure will misread a pending approval as an error. Developers on API v26 should download the latest client libraries once v26.2 ships for support for the new error code. Google’s advice: review and update that code before December 7, so the change does not surface as a fault in an integration.
Our Read
The substance here is smaller than the deadline suggests. Nothing here changes which actions need a second approver, or who that approver can be. What changes is plumbing: when an invitation comes into existence, how stale requests are reported, and how many reviews one call clears. It is a maintenance release with a hard date, not a new security policy.
Even so, the date deserves respect, because silent breakage is the risk. An integration assuming a resource name is always returned will not crash loudly; it will quietly mishandle invitations waiting on a second administrator in production, with no error to catch.
Google is making a similar December change elsewhere: image extraction in Performance Max campaigns switches on by default from December 4. December is becoming a month of small defaults with real consequences for anyone who has not read the release notes, and for the advertisers whose campaigns those defaults quietly reshape.
Why It Matters
Multi-party approval exists because Google Ads accounts are a prime target for takeovers, and a second administrator is the simplest check on a compromised login. The December changes tighten the mechanics around that check without changing who must approve what. For agencies managing accounts, the batch limit is an improvement: 100 reviews cleared in one call replaces 100 round trips.
Background
Multi-party approval arrived in the Ads API in late June, when version 24.2 introduced the mechanism for sensitive operations: user invitations and access level updates. The rollout began on July 27, and Google’s help pages say administrators have 20 days to approve or reject a request before it expires. The December update is the system’s first revision since it launched.
Source: Google Ads Developer Blog and PPC Land report
0 Comments