help menu

Join us on the Community Forums!

  • Community Guidelines

    The Fitbit Community is a gathering place for real people who wish to exchange ideas, solutions, tips, techniques, and insight about the Fitbit products and services they love. By joining our Community, you agree to uphold these guidelines, so please take a moment to look them over.

  • Learn the Basics

    Check out our Frequently Asked Questions page for information on Community features, and tips to make the most of your time here.

  • Join the Community!

    Join an existing conversation, or start a new thread to ask your question. Creating your account is completely free, and takes about a minute.

Not finding your answer on the Community Forums?

Cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 

OAuth refresh_token expiration

‎05-04-2023 17:55 - edited ‎05-04-2023 18:02

‎05-04-2023 17:55 - edited ‎05-04-2023 18:02

Hello

We have some issues related to the refresh_token expiration.

I asked chat-GPT:

ahmadradwan_0-1683248107461.png

Yes, Fitbit OAuth refresh tokens can expire. The expiration time for a refresh token is determined by Fitbit and may vary. According to Fitbit's documentation, refresh tokens may expire after 1 year of inactivity or if a user revokes access to your application. Additionally, if a user changes their password, their refresh token will be invalidated and they will need to reauthorize your application. Therefore, it's important to have a mechanism in place to handle refresh token expiration and refresh them as needed to ensure continued access to the user's data.

 

Is this correct?
Thanks in advance

Best Answer
0 Votes
0 REPLIES 0