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: 

Invalid Consumer Key

‎10-24-2017 10:52

‎10-24-2017 10:52

I have an app that uses OAuth to integrate with Fitbit and nightly pulls Step information.  I moved the app to a new server on September 28th copying over the same code, configuration, and database.  Since then I am not able to successfully connect to the API.  I'm getting the error "Invalid consumer key: XXXXXX" with the consumer key for may application.  

 

Could something need to be reset or changed when we switched servers?

 

Thanks. 

Best Answer
0 Votes
1 REPLY 1

‎10-30-2017 16:08

‎10-30-2017 16:08

hello @davekerber, are you using OAuth1.0a? 

The message that you posted can only be produced by OAuth1.0a and Fitbit currently does not supports OAuth1.0a as we deprecated it long time ago. You'll need to migrate your code to start using OAuth 2.0 instead.

 

Best Answer
0 Votes