Google Ads API User Access Approval: What Agencies Must Do
By Prashant Kumar Pandey, Founder, Digital Prashant Published 22 Nov 2026 · 7 min read
Quick answer
From the week of 7 December 2026, Google Ads API user access approval works differently: invitations that need multi-party approval aren't created until a second admin approves, so no resource name comes back. Agencies with tools that add users must update code, keep two admins per account and approve requests within 20 days.
If your agency adds people to client Google Ads accounts through a tool, a script built by a developer, or an onboarding dashboard, one date matters this month: the week of 7 December 2026. That's when Google changes Google Ads API user access approval under its multi-party approval system. The change is small in code, but if your tools aren't ready, new users can look "invited" in your system when Google hasn't actually created anything yet.
Here's what changed, who needs to act, and a simple checklist for both developers and account managers.
What is multi-party approval in Google Ads?
Multi-party approval (MPA) is Google's safety check for sensitive access changes. Google's Ads help page lists them as "adding a new user, removing an existing user, or changing user roles." When someone requests one of these, the request goes to the account's administrators, and a different admin has to approve it before it takes effect.
A few rules from Google's help page are worth knowing:
Administrators have 20 days to approve or reject a request. After that it shows as "Expired".
Admins of a manager account can approve requests for linked sub-accounts.
"Read-only roles and API users are exempt from this approval process."
Google Ads support can't approve or deny a request on your behalf.
If an account drops to a single administrator, multi-party approval is paused.
In the Google Ads interface you'll find pending items under Admin > Access and security, in "Pending invitations" (Review request) and a "Security requests" tab.
Google first brought MPA to the API in a Developer Blog post on 25 June 2026, with rollout starting 27 July 2026. That post said access changes "will only take effect once the multi-party review is successfully approved."
What changes in the Google Ads API from 7 December 2026?
Google's Ads Developer Blog post of 4 November 2026 lists three changes to Google Ads API user access approval, arriving the week of 7 December:
Change
What it means in practice
MutateCustomerUserAccessInvitation waits for approval before creating the invitation
If MPA applies, the invitation resource isn't created yet. Google says "The resource_name field is not populated in such cases."
New error STALE_MULTI_PARTY_AUTH_REQUEST
Returned when the target was changed or deleted before approval. It arrives in API v26.2; v23 to v25 return UNKNOWN with the stale code in unpublished_error_code.
ResolveMultiPartyAuthReview handles up to 100 reviews per call
Approving in bulk gets easier for tools that manage many accounts.
Google's instruction is direct: "If you use multi-party approvals, review and update your code to reflect the new API behavior before December 7, 2026."
Why the empty resource_name matters
Plenty of internal tools do something like this: send an invite, read back the resource name, save it as "invitation sent". From the week of 7 December, when an invite needs approval, there's nothing to read back. A tool that assumes it's always there may crash, log an error, or quietly mark the user as invited when they aren't. The person you added then waits for an email that never comes, and your account manager wastes a day chasing it.
Who needs to act on Google Ads API user access approval?
Not everyone. Use this quick test:
You must act if your agency, or a vendor you pay, invites users, changes roles or removes users through the Google Ads API. Common examples: client onboarding portals, access-management dashboards, in-house tools for big manager accounts.
Ask your vendor if you use third-party reporting, bidding or agency platforms that touch user management. Google's post doesn't name specific tools, so the only reliable answer comes from the vendor.
You can probably relax if your team adds users by hand in the Google Ads interface. You still follow MPA in the interface, but the API change doesn't affect you.
What about Google Ads scripts? Google's 4 November post doesn't mention scripts at all. Most scripts read reports or change bids and budgets, not user access. If you have a script that manages users, test it before 7 December rather than assume.
A checklist for developers
If you own the code, here's what we'd check this week:
Search your code for MutateCustomerUserAccessInvitation and any place that reads resource_name from its response.
Handle the empty case. Treat a missing resource name as "pending approval", not as an error or a success.
Track the review instead. Google's June post explains how to find pending reviews with a GAQL query on multi_party_auth_review, filtered to PENDING.
Add the new error. Catch STALE_MULTI_PARTY_AUTH_REQUEST (v26.2) and the UNKNOWN + unpublished_error_code pattern on v23–v25. Show a clear message such as "This request is out of date, please resend."
Batch approvals with ResolveMultiPartyAuthReview if you manage many accounts; it now accepts up to 100 reviews per call.
Test on a non-critical account before the change reaches your main manager account.
A checklist for agency owners and account managers
You don't need to read API docs to stay safe when Google Ads API user access approval changes. Do these five things:
Make sure every key account has at least two active admins. One admin means approvals can stall or pause; nobody wants to wait on a person who's on leave.
Agree who approves. Pick a named second approver on your side and on the client side, and tell them to expect requests.
Check "Security requests" weekly. Requests expire after 20 days; an expired one means starting again.
Ask vendors in writing: "Are you ready for the 7 December Google Ads API multi-party approval change?" Keep the reply.
Update your onboarding SOP. Add a line: "Access can stay pending until a second admin approves; check status before chasing the client."
India and US context
For agencies in India managing US client accounts (and US agencies using offshore teams), the 20-day window is generous, but time zones still slow approvals. A request sent at 6 PM in Gurugram lands at 7:30 AM in New York in winter, when the client admin may not check Google Ads for days. Our habit: send access requests at the start of the client's working day and message the approver at the same time. If you outsource account work, our guide on how white label PPC works covers account ownership and access in more detail.
Indian advertisers working directly in their own accounts mostly won't feel this change. The ones who will are agencies and in-house teams that built their own tools on the API.
Related API change: developer tokens
Separately, Google's Ads Developer Blog post of 10 September 2026 described a new onboarding flow in which API access levels come from the Google Cloud project, and said developer tokens are being phased out, with Google planning to reject them in a future major version. That's a different project from MPA, but if your developer is already updating code for 7 December, it's worth asking them to review the onboarding changes in the same sprint.
Assuming "invite sent" means access granted. Under MPA it can mean "waiting for a second admin".
Running accounts with a single admin. It weakens security and can pause approvals.
Ignoring expiry. Twenty days goes quickly during Black Friday and year-end campaigns.
Not asking vendors. If a tool breaks on 7 December, you'll find out when a new hire can't log in.
Granting admin to everyone to "avoid approvals". Give people the lowest role they need; read-only users don't trigger MPA anyway.
Need a second pair of eyes?
If you're not sure whether your setup is affected, we're happy to look at how your agency manages client access and tools. Book a free 30-minute strategy call and bring your list of tools.
What is changing with Google Ads API user access approval?
From the week of 7 December 2026, when an access invitation sent through the Google Ads API needs multi-party approval, Google won't create the invitation until it's approved, so the response has no resource name. Google is also adding a new stale-request error in API v26.2 and letting tools resolve up to 100 pending reviews in one call.
Who needs to act before 7 December 2026?
Anyone who invites users, changes roles or removes users through the Google Ads API: agencies with in-house tools, onboarding portals and access dashboards. If you use third-party platforms, ask the vendor whether they manage user access through the API and whether they're ready. Teams that add users by hand in the Google Ads interface don't need to change any code.
What happens if a request isn't approved in time?
Google's help page says administrators have 20 days to approve or reject a multi-party approval request. After that, it shows as Expired and nothing changes in the account, so the user isn't added or removed. You'd need to send a new request. Google Ads support can't approve requests for you, so set a named second approver in advance.
Does this affect Google Ads scripts?
Google's 4 November 2026 announcement doesn't mention Google Ads scripts. Most scripts handle reports, bids and budgets rather than user access, so they're unlikely to be affected. If you have a custom script or tool that adds or removes users, test it before 7 December 2026 and check how it handles a pending approval.
How do I check pending approval requests?
In the Google Ads interface, go to Admin, then Access and security. Pending items appear under Pending invitations with a Review request option, and in the Security requests tab. Developers can list pending reviews through the API with a GAQL query on the multi_party_auth_review resource, filtered to the PENDING status, as Google's June 2026 developer post explains.
Prashant Kumar Pandey
Founder of Digital Prashant and a performance marketer since 2018. He has generated 10,000+ leads with Meta Ads and managed ad budgets up to ₹40 lakh a month. View profile.