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: 

OAuth 2.0 get encoded user id after authorization.

‎06-29-2015 23:37 - last edited on ‎07-07-2015 16:08 by SunsetRunner

‎06-29-2015 23:37 - last edited on ‎07-07-2015 16:08 by SunsetRunner

Hi There,

 

Like oauth 1.0 , after authorization can we get encoded user id in oauth 2.0 also?

 

{ "access_token": "eyJhbGciOiJ....Ulpc", "expires_in": 600, "refresh_token": "...", "token_type": "Bearer" }

Best Answer
Labels:
0 Votes
1 REPLY 1

‎07-07-2015 16:07 - edited ‎07-07-2015 16:08

‎07-07-2015 16:07 - edited ‎07-07-2015 16:08

@Pramod wrote:

Hi There,

 

Like oauth 1.0 , after authorization can we get encoded user id in oauth 2.0 also?

 

We will be adding this functionality very soon! Thanks for the suggestion.

Best Answer
0 Votes