# Refresh Token 90 Day Expiration **URL:** \ **Category:** Meetings\ **Created:** [October 27, 2023, 1:10pm UTC](https://devforum.zoom.us/t/refresh-token-90-day-expiration/97457 "2023-10-27T13:10:45Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![scoreboston](https://avatars.discourse-cdn.com/v4/letter/s/77aa72/32.png) [@scoreboston](https://devforum.zoom.us/u/scoreboston)\ **Post date:** [October 27, 2023, 1:10pm UTC](https://devforum.zoom.us/t/refresh-token-90-day-expiration/97457/1 "2023-10-27T13:10:45Z")
Changing the Refresh token expiration to 90 days is creating big problems for our app which has casual users. Re-authorizing the app manually is not an option. Is there a workaround for this or an api request to get a new access code/refresh token when we encounter this problem? Thanks ---
**Author:** ![ojus.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/ojus.zoom/32/734_2.png) [@ojus.zoom](https://devforum.zoom.us/u/ojus.zoom)\ **Post date:** [October 27, 2023, 4:18pm UTC](https://devforum.zoom.us/t/refresh-token-90-day-expiration/97457/2 "2023-10-27T16:18:23Z")
@scoreboston We cannot change the validity of the refresh tokens, however, you can setup a logic where you manually make an API call to generate a new access token (which will also give you a refresh token). If your refresh token expires, then your users need to manually reauthorize the app ---
**Author:** ![scoreboston](https://avatars.discourse-cdn.com/v4/letter/s/77aa72/32.png) [@scoreboston](https://devforum.zoom.us/u/scoreboston)\ **Post date:** [October 30, 2023, 5:46pm UTC](https://devforum.zoom.us/t/refresh-token-90-day-expiration/97457/3 "2023-10-30T17:46:07Z")
Thanks, So something like keeping track of when a refresh token is going to expire and manually doing the API call to generate a new one is what you are suggesting. Are their limits to the number of those API requests that can be made for different users in a day? or other time period?