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: 

Token request failing with 403

‎06-12-2025 04:51

‎06-12-2025 04:51

We are having an issue with the token request failing with a 403. This is only happening in one of our environments with a specific clientID. Tested using Fitbit Web API explorer, and curl. Screenshots attached for reference. Any idea what could be the cause?

Fitbit-403.png

Fitbit-403-curl.png

 

 

Best Answer
Labels:
0 Votes
1 REPLY 1

‎07-11-2025 15:44

‎07-11-2025 15:44

Hi @getrealhealth,

Thanks for reporting this and I'll be happy to take a look. Could you please PM me your basic token that you're using in your authorize request? Also, can you tell me what application type your application is set to (Personal/Server/Client)?

Best Answer
0 Votes