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: 

Could we assume Bearer to be the only token type in Fitbit OAuth 2.0?

‎11-21-2015 20:03

‎11-21-2015 20:03

Could we assume Bearer to be the only token type in Fitbit OAuth 2.0? Thanks.

Best Answer
Labels:
0 Votes
2 REPLIES 2

‎11-22-2015 11:55

‎11-22-2015 11:55

I'm not sure I understand the question. Fitbit currently uses two types of Authorization headers in its OAuth 2.0 implementation: Basic and Bearer. There are two types of tokens: access and refresh. Only access tokens are used as Bearer tokens in an Authorization header.

Best Answer
0 Votes

‎11-22-2015 12:07

In response to JeremiahFitbit

‎11-22-2015 12:07

I guess my question has got answered. I am just wondering other token type like "MAC" will be used by Fitbit so that I have to implement the corresponding handler. Thank you.

Best Answer
0 Votes