Can we continue to use permanently the refresh token created by the credentials of the APP that you have not completed your review?

[mintia522]

Dear Team.

I am preparing for the successful completion of your review of my APP in order to go live with an APP that requires "sensitive scope".

There are a few issues that need to be addressed, and while I am working hard on them, I cannot predict when your review will be completed.

The review is not yet complete, but I would like to request OAuth authentication for my client using the APP credentials. I would like to use the refresh token generated by it to call the API.

However, since your review is not complete, if I do that, I will get a warning before going to the OAuth authentication screen.I have a concerns about that.

 Can we continue to use permanently the refresh token created by the credentials of the APP that you have not completed your review? Do you place any restrictions on such tokens? Your response to these questions will help our business a lot. I'm eager for a response.

Best,

[AdWords API and Google Ads API Forum]

Reposting the last inquiry (https://groups.google.com/g/adwords-api/c/bxfgnLR1_Ts) from the forum as it wasn't routed to our support queue.

Cheers,

Peter Laurence Oliquino

Google Ads API Team

[Google Ads API Forum Advisor]

Hi,

Thank you for posting your concern.

Could you confirm if what you mean for review of your APP is the RMF review that is discussed here or the approval of the developer token? 

Either of the two, it appears that you can generate Oauth2 credential ahead, using the email address / user account that has access to the production MCC, while waiting for the updates on the review. Afterwards, you may then wait until the said approval has been confirmed before performing API requests on your Production Google Ads accounts.

Regards,

Ernie John Blanca Tacata Google Ads API Team

ref:_00D1U1174p._5004Q2IvDqG:ref