Earlier this year, the Google Ads API started requiring multi-party approvals (MPA) when performing sensitive API actions. Starting the week of December 7, 2026 , we are introducing additional changes to improve the developer experience for multi-party approvals.
What’s changing?
Deferred access invitation creation: If a multi-party approval is required, the CustomerUserAccessInvitationService.MutateCustomerUserAccessInvitation resource_name approved , the access invitation resource is available from the review results . Currently, this method creates the invitation and returns the resource_name
New error code for stale requests: We will start returning a new MultiPartyAuthReviewError.STALE_MULTI_PARTY_AUTH_REQUEST error code in the partial failure field when a pending MPA request is no longer valid because the target resource was modified or deleted after the review was created. This error code will be introduced in the upcoming v26.2 release. Older API versions (v23 through v25) will return a MultiPartyAuthReviewError.UNKNOWN error, and the unpublished_error_code GoogleAdsError.details MultiPartyAuthReviewError.STALE_MULTI_PARTY_AUTH_REQUEST.
Increased limits for MPA reviews: You can resolve up to 100 pending MPA reviews in a single call to the MultiPartyAuthReviewService.ResolveMultiPartyAuthReview
Action required
If you use multi-party approvals, review and update your code to reflect the new API behavior before December 7, 2026 . If you are using v26 of the Google Ads API, download the latest client libraries after v26.2 is released to get support for the new STALE_MULTI_PARTY_AUTH_REQUEST error code. Refer to our technical guides to learn more about multi-party approvals. For technical support issues, reach out to Google Ads API support . If you have any questions or want to discuss this post, reach out to us on our Google Advertising and Measurement Community Discord server .
Anash P. Oommen , Google Ads API Team
