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: 

Redirected url link sent an expired code

‎11-17-2022 06:49

‎11-17-2022 06:49

Guys hello, I need your help and I seek your wisdom please. Here is my problem. During Fitbit connection flow after permissions were selected I have been always receiving an invalid code. What did I do wrong. Here is my oauth2 request: 

/oauth2/authorize?client_id=MyClientID&redirect_uri=https://ppserver-2865.sbx.huma.com&response_type=code&scope=activity+heartrate+location&code_challen...=MyCodeChallenge&code_challenge_method=S256&expires_in=604800

So I cannot change this code to the access_token / refresh_token(

Best Answer
0 Votes
1 REPLY 1

‎11-17-2022 07:09

‎11-17-2022 07:09

Just a small clarification: I sent code to our backend, and they tried to change it to tokens, but receive invalidation error.Just a small clarification: I sent code to our backend, and they tried to change it to tokens, but receive invalidation error.

Best Answer
0 Votes