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.
Fitbit Developers oversee the SDK and API forums. We're here to answer questions about Fitbit developer tools, assist with projects, and make sure your voice is heard by the development team.
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.
Fitbit Developers oversee the SDK and API forums. We're here to answer questions about Fitbit developer tools, assist with projects, and make sure your voice is heard by the development team.
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.