What is the relationship between the OAuth2 authenticated user of GoogleAdsAPI and the user of the MCC account for testing?

[Yuta]

Hi,

What is the relationship between the OAuth2 authenticated user of GoogleAdsAPI and the user of the MCC account for testing?
If the OAuth2-authenticated Google account is no longer the user of the MCC account for testing
Will requests to the API be disabled?

For example.
１. create a test MCC account.
２. Add the users a...@google.com and b...@google.com to the test MCC account.
３. Perform OAuth2 authentication on a...@google.com.
４. Remove a...@google.com from the test MCC account.
In this case, will the authentication information that was used for OAuth2 authentication with "a...@google.com" in "3." be invalidated?

Thanks,
Yuta.

[Google Ads API Forum Advisor]

Hello Yuta,

Thanks for reaching out to the Google Ads API forum. With regards to your question, the developer token is not restricted to only one Google Ads account. Once your token is approved, you can use the same token for requests against all your Google Ads accounts, even if they're not linked to the Google Ads Manager Account associated with the token. Feel free to use our Quickstart guideline for getting more information on the Ads API. Please refer to this page for getting more information on Test Accounts.

Here are some key points shared below for your understanding:

• A company should have only one developer token.
• Once a client ID from a Google Cloud project is used with a developer token, the client ID is bound to the developer token and can't be used with another developer token. In other words:
  • A developer token can be used with multiple client IDs.
  • However, a client ID can be used with only one developer token.

Hope this helps, feel free to reply back to us if you have any questions.

Best Regards,

Jakeia Google Ads API Team

 

ref:_00D1U1174p._5004Q2a2mfx:ref

[Google Ads API Forum Advisor]

Hello Yuta,

Thank you for following up. With regards to your question, all Google Ads API calls must be authorized through OAuth 2.0 protocol for authentication and authorization.
Credentials for accessing Google's OAuth2 servers are required in order to authenticate and authorize Google Ads users. These credentials identify your app to Google, and allow you to generate OAuth tokens for managing Google Ads users. Access to Google OAuth2 credentials is managed from the Google API Console. OAuth2 enables your Google Ads API client app to access a user's Google Ads account without having to handle or store the user's login info. Please refer to the page for getting more information. Let me know if you have any questions.

Best regards,

Jakeia Sabrina Google Ads API Team

 

ref:_00D1U1174p._5004Q2a2mfx:ref