09-27-2019 06:36
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

09-27-2019 06:36
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
What is the diference between Client_id used in token request and user_id returned in result of this request?
Answered! Go to the Best Answer.
Accepted Solutions
09-27-2019 14:18
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post



09-27-2019 14:18
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
- Who Voted for this post?
Hi @SamuelMira,
Client_id is the ID assigned to your application after registering it at dev.fitbit.com. This is used to identify your application when making a request to Fitbit during the authorization process for a user. Upon user consent, Fitbit redirects the user back to your application using your redirect URI and provides you with an access token and refresh token for the user, by associating the tokens to the user's user_id. For more information, see our documentation for Obtaining Consent.
09-27-2019 14:18
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post



09-27-2019 14:18
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
- Who Voted for this post?
Hi @SamuelMira,
Client_id is the ID assigned to your application after registering it at dev.fitbit.com. This is used to identify your application when making a request to Fitbit during the authorization process for a user. Upon user consent, Fitbit redirects the user back to your application using your redirect URI and provides you with an access token and refresh token for the user, by associating the tokens to the user's user_id. For more information, see our documentation for Obtaining Consent.
10-07-2019 07:47
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

10-07-2019 07:47
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
@JohnFitbit Thanks for your answer.

