As part of improving security for Google Ads accounts, the Google Ads API will start requiring multi-party approvals when performing sensitive API actions. This is part of a broader change in Google Ads that requires multi-party approvals to perform sensitive actions in your Google Ads account. These important security updates will start rolling out starting on July 27, 2026 , and will be enabled for all users over the next few weeks.
What is changing?
When this change goes live, the following API calls will change their behavior.
Inviting a user
If you use the CustomerUserAccessInvitationService.MutateCustomerUserAccessInvitation invite a new user to manage a Google Ads account, the Google Ads API now evaluates whether multi-party approval may be necessary. In cases where our servers determine that a review is required, the system will pause the standard workflow and will not immediately generate a CustomerUserAccessInvitation MultiPartyAuthReview resource name provided in the response. Once the pending review receives approval from a second account administrator, the CustomerUserAccessInvitation
Updating or terminating a user’s access
If you use the CustomerUserAccessService.MutateCustomerUserAccess update operation or revoke access using the remove operation , the Google Ads API now evaluates whether multi-party approval may be necessary. In cases where our servers determine that a review is required, the API generates a MultiPartyAuthReview resource name . Your requested modifications will remain pending and will only take effect once the multi-party review is successfully approved by a second account administrator. The CustomerUserAccess
How do I approve a multi-party approval request?
You can fetch a pending MultiPartyAuthReview GoogleAdsService.Search GoogleAdsService.SearchStream
SELECT
multi_party_auth_review.resource_name,
multi_party_auth_review.multi_party_auth_review_id,
multi_party_auth_review.creation_date_time,
multi_party_auth_review.request_user_email,
multi_party_auth_review.operation_type,
multi_party_auth_review.justification,
multi_party_auth_review.target_resource,
multi_party_auth_review.customer_user_access_review.old_customer_user_access,
multi_party_auth_review.customer_user_access_review.new_customer_user_access,
multi_party_auth_review.customer_user_access_invitation_review.new_customer_user_access_invitation
FROM multi_party_auth_review
WHERE multi_party_auth_review.review_status = 'PENDING'
A pending MultiPartyAuthReview MultiPartyAuthReviewService.ResolveMultiPartyAuthReview
What do I need to do?
If your application uses these methods, make sure to update it to handle the multi-party approval workflows before July 27, 2026 . We have added support for multi-party approvals to all the major versions of the API (v24.2, v23.3, v22.2 and v21.2). If you are using an official client library, make sure to download their latest version . You can refer to the following guides to learn more about these changes, which cover details on
For any questions or further discussion regarding this update, please connect with us on the "Google Advertising and Measurement Community" Discord server . For technical support issues, reach out to https://support.google.com/google-ads/contact/google_ads_api
Anash P. Oommen , Google Ads API Team
