
Hi,
Thank you for reaching out to Google Ads API Forum.
I can see that you've already raised this same concern in another thread with the subject Google ads api Refresh Token Life Time. We have already replied to the other thread. For better tracking of the issue, kindly continue discussion only in a single thread instead.
To reiterate what was mentioned on that thread, kindly note that a Google Cloud Platform project with an OAuth consent screen configured for an external user type and a publishing status of Testing is issued a refresh token expiring in 7 days. To handle this, you may indeed go to the Google API Console and navigate to the OAuth consent screen. Then change the publishing status to In production following these instructions to avoid the refresh token expiring in 7 days. You may also see these Unverified apps (https://support.google.com/cloud/answer/7454865) for prevention tips.
![]() |
Google Ads API Team |
Hi lin,
Thank you for the reply.
Kindly note that even when changing the publishing status to In production will avoid the refresh token expiring in 7 days, there's still a reason for the refresh token to get expired. You may refer to this Google Identity Platform OAuth documentation (https://developers.google.com/identity/protocols/oauth2#expiration) to see the reasons why the refresh token might stop working even though this is already in production.