Hi Martin,
Thank you for providing more details to your concern.
Before proceeding to your concern, I would like to inform you first that I am going to delete your latest post as it contains your developer token. Also, since your developer token has been exposed privately, then I would suggest doing a
developer token reset. Please note that a reset will immediately invalidate your previous token, so any API requests using the old token will fail. However, a reset will not trigger a re-review and approval for the new developer token. You can start using the new developer token immediately.
Moving forward, I can see that your developer token already has standard access so you shouldn't encounter the said error. With this, could you try the new developer token after reset and retry the API request again? If the error persists, please provide the complete
request and
response logs with
request ID and
request header generated on your end so that I can discuss it to the rest of the team.
You can provide it via
Reply privately to author option. If this option is not available, then send it instead on this email address
googleadsa...@google.com.
Regards,
 |
Ernie John |
Google Ads API Team |
|
|
|

ref:_00D1U1174p._5004Q2aNxmu:ref