DEVELOPER_TOKEN_NOT_APPROVED for token that was previously working

34 views
Skip to first unread message

Mars Data

unread,
Sep 12, 2022, 7:08:06 AM9/12/22
to Google Ads API and AdWords API Forum
Hi,

We use the Google Ads API to upload audiences to Google Ad Manager accounts for different campaigns that we run. A while back we suddenly started getting this error "DEVELOPER_TOKEN_NOT_APPROVED" despite the Developer Token being used hundreds of times previously.

I can run the CustomerService.list_accessible_customer() command with the Developer token without error, but every other command/service available fails not because of the DEVELOPER_TOKEN_NOT_APPROVED. If I provide the Developer Token and Request ID is it possible to determine the status of the Developer token?

I've tried to go the route of setting up a new Developer Token but I've now found that the Google Project can only be associated with one Developer Token, so I would have to create a whole new Google Project. Because a lot of this was initially set up by another agency we don't have a lot of the information on how this was set up, so I don't actually know (or have access to) what is presumably the top level Ad Manager Account so I don't know if creating a new Developer Token is even the correct approach here as we have lots of different Ad Manager Accounts that we need to link to. Now that I know I can only have one Developer Token is this approach even going to work, can I 'deploy' that Developer Token to other Ad Manager Accounts that I have access to but aren't linked to each other?

Or finally, is there a way of swapping the Developer Token that's associated with the Google Cloud Project, or is there a way of actually confirming what Developer Token is associated with the Google Cloud Project?



Thanks,





Google Ads API Forum Advisor

unread,
Sep 12, 2022, 10:28:45 AM9/12/22
to adwor...@googlegroups.com
Hi,

Thank you for reaching out to us.

You may note that the DEVELOPER_TOKEN_NOT_APPROVED error might be connected to your account access level. If your API access is still in test, the presented issue is caused by making a call against a production account with a developer token only approved for test access. You can apply for Basic Access by following the steps outlined here .

Moving forward to this, “can I 'deploy' that Developer Token to other Ad Manager Accounts that I have access to but aren't linked to each other?
-No, this is because using other credentials without adding it first as a user would most likely result in user permission denied errors.

And for this, “is there a way of swapping the Developer Token that's associated with the Google Cloud Project?"
-I would suggest that you reach out to the Compliance team instead via this contact form, as they are more equipped to provide guidance on this matter.

Also for this, "Is there a way of actually confirming what Developer Token is associated with the Google Cloud Project?
-There is no way to find if any Developer Token is associated with the Google Cloud Project. However, if you make request to GCP project where it is paired to other developer token, then it should receive developer_token_prohibited error.

Best regards,
Google Logo
Heidi
Google Ads API Team
 


ref:_00D1U1174p._5004Q2eNIyH:ref
Reply all
Reply to author
Forward
0 new messages