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: 

400 bad request when re-refreshing a token - Urgent

‎11-13-2019 03:43 - edited ‎11-13-2019 03:58

‎11-13-2019 03:43 - edited ‎11-13-2019 03:58

Hey guys,

 

I'm currently using the fitbit API's oAuth method to request a new refresh code, which i can use in subsequent requests to the API on other methods.

 

On each of my calls to get information about the users steps or sleep, i am using this method to update both the refresh token and the access token in the database.

 

On the first, the insertion of the refresh and access token in the database is successful, and the call to get the steps of the user works. However once the call to get the sleep info runs, where the refresh token and access token are refreshed and updated in the database, a 400 bad request error is returned.

 

Any ideas on why?

 

Thank you

Best Answer
Labels:
0 Votes
1 REPLY 1

‎11-13-2019 11:16

‎11-13-2019 11:16

Hi @Rodrialves,

 

Welcome to the forums!

 

I recommend checking out our troubleshooting guide for solutions to common refresh token errors. 

 

If the scenarios provided above don't fit the issue you are experiencing, please PM me your Client ID, the user id of the customer you were refreshing the token for, and the timestamps of when you were receiving the errors (within the last 7 days).

 

I hope this helps. Let me know if you have any additional questions.

Best Answer