Cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

OAuth 2.0 expiresIn value

ANSWERED

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.

Best Answer
0 Votes
1 BEST ANSWER

Accepted Solutions

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.

View best answer in original post

Best Answer
0 Votes
3 REPLIES 3

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
0 Votes


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
0 Votes

@SteppyBob Yeah that needs to be updated since the default is 8 hours. Thanks.

Andrew | Community Moderator, Fitbit

What motivates you?

Best Answer
0 Votes