03-17-2016 15:38
03-17-2016 15:38
Can I make assumptions about the length of the access and refresh tokens?
Answered! Go to the Best Answer.
11-14-2016 18:09
Fitbit Developers oversee the SDK and API forums. We're here to answer questions about Fitbit developer tools, assist with projects, and make sure your voice is heard by the development team.
11-14-2016 18:09
Your app should accomodate 1,024 bytes per token.
03-18-2016 13:32
03-18-2016 13:32
Also, is there an upper bound for the length of each type of token?
11-12-2016 17:33
11-12-2016 17:33
I'd also like to know
Best Answer11-12-2016 19:11
Community Moderator Alumni are previous members of the Moderation Team, which ensures conversations are friendly, factual, and on-topic. Moderators are here to answer questions, escalate bugs, and make sure your voice is heard by the larger Fitbit team. Learn more
11-12-2016 19:11
@m4olivei You can select the lifetime of the access token.
Authorization Code Grant Flow: 1 hour or 8 hours (defaults to 8 hours)
Implicit Grant Flow: 1 day / 1 week / 30 day / 1 year (defaults to 1 day)
Refresh tokens do not expire until they've been used, or if the user goes through the authorization process again.
Best Answer11-14-2016 05:56
11-14-2016 05:56
Thanks, but we're asking about the character length of the token. Is there a defined length of token, or can it vary. Is it different for the access_token and refresh_token?
Best Answer11-14-2016 18:09
Fitbit Developers oversee the SDK and API forums. We're here to answer questions about Fitbit developer tools, assist with projects, and make sure your voice is heard by the development team.
11-14-2016 18:09
Your app should accomodate 1,024 bytes per token.