Refresh token for internal app.

[Sophie Quenard]

Hi, i'm using a self hosted application to get our google ads data.  I have this working.  The app is privately hosted and no actual users log into it, it's authorised to connect to the google ads api.  This is working but the refresh token seems to be failing to update the access token after a week or two.  I believe that this is because the app is External but in testing status. 

I need the refresh token to keep working but I'm not sure the best way to do this.  I can publish External app and make it production statusbut then it needs to be public facing which is not what I want.  There is also the option to make it internal but this is not permitted unless the associated user is part of workspaces and I don't know the implications of this.  Could anyone advise of the best way to go?

Thanks

[Google Ads API Forum Advisor]

Hi Sophie,

Thank you for reaching out to us.

With regard to your concern, the refresh token expires or might stop working due to one of the following reasons:

• The user has revoked your app's access.
• The refresh token has not been used for six months.
• The user changed passwords and the refresh token contains Gmail scopes.
• The user account has exceeded a maximum number of granted (live) refresh tokens.
• If an admin set any of the services requested in your app's scopes to Restricted (the error is admin_policy_enforced).
• For Google Cloud Platform APIs - the session length set by the admin could have been exceeded.

With that, we would recommend to write your code to anticipate the possibility that a granted refresh token might no longer work.
 

This message is in relation to case "ref:_00D1U1174p._5004Q2mUCxA:ref"

Thanks,
 

Google Ads API Team