Fitbit API Authentication

[vigneshdev]

I am writing to you as a developer working on a project that involves Fitbit account synchronization. As part of the authentication process, we obtain and store access codes and refresh tokens for users.

We have encountered an issue where previously issued tokens expire, causing problems for users who attempt to add the same Fitbit account using their Fitbit user ID. We are currently restricting this action, but we would like to explore potential solutions to ensure a smooth user experience.

Could you please provide guidance on best practices for handling token expiration and potential workarounds for this issue? Your expertise would be greatly appreciated.

[Gordon-C]

Hi @vigneshdev 

When you say the token expires, do you mean the access token or refresh token?   Also, you said this is "causing problems for users who attempt to add the same Fitbit account using their Fitbit user ID".  Is this when users are trying to complete the authorization flow again after they have completed before?