Rotating developer token with standard access

[rahul...@decision-tree.com]

Hi Guys,

We have a google ads developer app and token that we have been using to fetch GoogleAds data. Now, based on our new policy we need to rotate all google credentials every 6 month and that includes the GoogleAds developer token too. However, when we tried to use the new developer token in our existing app, it says, "Developer token prohibited for the project ******". 

Based on google docs, we can see that we have to create a new google API project to use a new developer token. But that means, we will have to re-verify the app which takes a lot of time.

Is there a way to use the new developer token in the same app with minimum downtime? Our existing app is already verified.

Thanks,

Rahul

[Google Ads API Forum Advisor]

Hi,

Thank you for reaching out to the Google Ads API support team.

I understand that you are getting the 'DEVELOPER_TOKEN_PROHIBITED' error. Please note that each Google API Console project can be associated with the developer token from only one manager account. Once you make a Google Ads API request, the developer token is permanently paired to the Google API Console project. 

If you want to switch the account, you'll need to create a new Google API Console project for Google Ads API requests that use the new manager's token. If you don't use a new Google API Console project, you'll get a DEVELOPER_TOKEN_PROHIBITED error when making a request. Also, Please check if you have the correct access level to the Google Ads account that you are accessing.

As per this section of the developer token reset guide, it only explicitly states that the old token can no longer be used. This indicates that the new token (that belongs still to the same MCC account) can be used with your existing Google Cloud project’s credentials. If the new developer token doesn’t belong to the same MCC account, you need to create a new Google API Console project.

Thanks,
 

Google Ads API Team

Feedback
How was our support today?

               
[2025-03-12 12:27:52Z GMT] This message is in relation to case "ref:!00D1U01174p.!5004Q02vH920:ref" (ADR-00293727)