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: 

Query parameter expires_in not working

‎06-10-2019 01:59

‎06-10-2019 01:59

I'm making request to authorize a user but it always returns 28800 as expires_in

 

Here is the URL 

https://www.fitbit.com/oauth2/authorize?response_type=code&client_id=xxxxxx&scope=activity%20heartra...

 

Whatever I put as expires_in it returns 28800

 

What is the issue?

Best Answer
Labels:
0 Votes
1 REPLY 1

‎06-10-2019 13:58

‎06-10-2019 13:58

Hi @awais78,

 

If your application type is currently set to using the Authorization Code Grant Flow, access tokens have a default expiration of 8 hours (28800 seconds). This cannot be changed.

 

However, if you'd like your users to be able to select how long your application can access their data, you will need to change your application settings to the Implicit Grant Flow. This authorization flow allows users to select how long they give consent to your application (1 day, 1 week, 30 days, or 1 year).

 

I hope this helps!

Best Answer