Hi, we're just starting to migrate over to OAuth 2.0 and noticed the 'expiresIn' value in the Access Token response (Authorization Code Grant Flow) comes back as: 28800.
The documentation says it should be 3600, so why is it coming back as 28800?
Many thanks.
Answered! Go to the Best Answer.
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.
We just released this. 🙂 Documentation will be updated shortly.
Our new default lifetime for refreshable access tokens is 8 hours. You can explicitly request a 1 hour access token by setting expires_in=3600 in your access and refresh token requests.
Best Answer
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.
We just released this. 🙂 Documentation will be updated shortly.
Our new default lifetime for refreshable access tokens is 8 hours. You can explicitly request a 1 hour access token by setting expires_in=3600 in your access and refresh token requests.
Best Answer
It appears that in API docs, the "Body Parameters" section has been updated to reflect the new 28800 default, but in the "Refreshing Tokens" section that follows, the copy reads:
When using the Authorization Code Grant flow, the access tokens have a one-hour lifetime.
Does this need to be updated as well, or am I mistaking this for something else?
Best Answer
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