Wednesday, November 4, 2026


Earlier this year, the [Google Ads API](https://developers.google.com/google-ads/api?utm_source=googleblog-adsdevs&utm_medium=blog&utm_campaign=adr-adsapi-mpa-changes&utm_content=learnmore-guide) started [requiring multi-party approvals](https://developers.google.com/ads/blog/posts/2026/06/multi-party-approvals-in-google-ads-api.md.txt) (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?

<br />


**Deferred access invitation creation:** If a multi-party approval is required, the `CustomerUserAccessInvitationService.MutateCustomerUserAccessInvitation` method will defer the creation of the access invitation resource until the multi-party approval request is approved. The `resource_name` field is not populated in such cases. Once the pending MPA request is [approved](https://developers.google.com/google-ads/api/reference/rpc/v26/MultiPartyAuthReviewStatusEnum.MultiPartyAuthReviewStatus.md.txt?utm_source=googleblog-adsdevs&utm_medium=blog&utm_campaign=adr-adsapi-mpa-changes&utm_content=learnmore-refdocs#approved), the access invitation resource is available from the [review results](https://developers.google.com/google-ads/api/reference/rpc/v26/ResolveMultiPartyAuthReviewResult.md.txt?utm_source=googleblog-adsdevs&utm_medium=blog&utm_campaign=adr-adsapi-mpa-changes&utm_content=learnmore-refdocs#customer_user_access_invitation). Currently, this method creates the invitation and returns the `resource_name` of the invitation, but doesn't perform additional actions like sending an invitation email until the associated MPA request is approved.


**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](https://developers.google.com/google-ads/api/reference/rpc/v26/ResolveMultiPartyAuthReviewResultOrError.md.txt?utm_source=googleblog-adsdevs&utm_medium=blog&utm_campaign=adr-adsapi-mpa-changes&utm_content=learnmore-refdocs#partial_failure_error) 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` field in `GoogleAdsError.details` will be set to `MultiPartyAuthReviewError.STALE_MULTI_PARTY_AUTH_REQUEST`.


**Increased limits for MPA reviews:** You can [resolve](https://developers.google.com/google-ads/api/reference/rpc/v26/ResolveMultiPartyAuthReviewOperation.md.txt?utm_source=googleblog-adsdevs&utm_medium=blog&utm_campaign=adr-adsapi-mpa-changes&utm_content=learnmore-refdocs#new_status) up to 100 pending MPA reviews in a single call to the `MultiPartyAuthReviewService.ResolveMultiPartyAuthReview` method. Currently, this method is limited to one review per API call.

### 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](https://developers.google.com/google-ads/api/docs/client-libs.md.txt?utm_source=googleblog-adsdevs&utm_medium=blog&utm_campaign=adr-adsapi-mpa-changes&utm_content=learnmore-clientlibs) after [v26.2 is released](https://developers.google.com/google-ads/api/docs/sunset-dates.md.txt?utm_source=googleblog-adsdevs&utm_medium=blog&utm_campaign=adr-adsapi-mpa-changes&utm_content=learnmore-guide#timetable) to get support for the new `STALE_MULTI_PARTY_AUTH_REQUEST` error code. Refer to our [technical guides](https://developers.google.com/google-ads/api/docs/oauth/multi-party-approvals.md.txt?utm_source=googleblog-adsdevs&utm_medium=blog&utm_campaign=adr-adsapi-mpa-changes&utm_content=learnmore-guide) to learn more about multi-party approvals. For technical support issues, reach out to [Google Ads API support](https://support.google.com/google-ads/contact/google_ads_api). If you have any questions or want to discuss this post, reach out to us on our [Google Advertising and Measurement Community Discord server](https://goo.gle/ads-and-measurement-discord).

[![Portrait of the author](https://developers.google.com/static/ads/blog/images/AD_cMMRmfdsXvZhyLvWsLuqqcScxtYI0ih7DPGCk8lTee140NzXH=s300.jpg)](https://g.dev/anash) - [Anash P. Oommen](https://g.dev/anash), Google Ads API Team

**Labels:**

[authorization](https://developers.google.com/ads/blog/feeds/labels/authorization.md.txt),

[google-ads-api](https://developers.google.com/ads/blog/feeds/labels/google-ads-api.md.txt),

[release](https://developers.google.com/ads/blog/feeds/labels/release.md.txt)