developer token

[ISMAIL TAIBANI]

Hi Google Ads API Team

A----we have standard access against one of our developer-token A on our Production-MCC and created Google API Console project on GCP so as per the doc (https://developers.google.com/google-ads/api/docs/first-call/dev-token) developer token is permanently paired with Google API Console project.

B----Now we have another running MCC for testing purpose with developer token B we have created Google API Console project for that as well. But that have basic access ,so API get exhausted because of daily limit of 15000 APIs. This cause blocker in our testing.so what can we do to resolve this issue.

1. should we use same developer token A and Google API Console project of B  and user access token of B to access B MCC account, 
2. should we use same developer token A and Google API Console project of A itself and user access token of B to access B MCC account, 
3. our you can provide standard access to our another MCC account developer token.
   

Note: B is not customer A or in anyway they are connect. And we don't want to

[Google Ads API Forum Advisor]

Hi Ismail,

Thank you for reaching out to our API support team.

Using the standard access developer token in your testing purposes can help in avoiding the operational limits you are encountering. However, the Google Cloud Projects that you used in both developer tokens A and B are already permanently paired to them respectively.

If you wish to use developer token A (standard access), you will need to create a new Google Cloud Project and OAuth credentials using a user / email address that has access to the other MCC, so that you can use credentials and authenticate without issues on your other MCC's account hierarchy.

As for asking for standard access approval, this also can be considered. However, do take note that the Compliance Team generally only approves 1 developer token per entity. Since you currently have both a standard access and basic access developer token, there may be some discussion later on with their team.

You may opt to reach out to the Compliance Team as well, via this contact form, for further insights on your developer token options.

Best regards,

Peter Laurence Google Ads API Team

ref:_00D1U1174p._5004Q2blw6T:ref

[ISMAIL TAIBANI]

so can we create another Google console API project for test and can use developer token A again. Our developer token A is already pair with one Google console API project for production.

so if i m understanding correctly one developer token A can be paired with two projects without any issue right ?

and this way we can keep our production and stage environment Google console API project separate using same developer token ?

[Google Ads API Forum Advisor]

Hi Ismail,

Thanks for getting back to us.

Kindly see below responses to your queries:

so can we create another Google console API project for test and can use developer token A again. Our developer token A is already pair with one Google console API project for production.

so if i m understanding correctly one developer token A can be paired with two projects without any issue right ?

>> Your understanding is correct. You may create another Google console API project for test and can use developer token A.

and this way we can keep our production and stage environment Google console API project separate using same developer token ?

>> Yes, you are correct in your understanding.

Let us know if you have any further questions.

Regards,

Yasar Google Ads API Team

ref:_00D1U1174p._5004Q2blw6T:ref