03-30-2022 00:57
03-30-2022 00:57
Hi team,
I am currently working on an application that requires me to get the fitbit health data after the the User is logged in. Now the issue I am facing is :-
1) For communicating with the fitbit api I need to register my account as a developer and register an application to get the client id. Not every user is capable of registering themselves as an developer and providing the client ID.
2) Without client ID is there a way to pull the user data?(The user will login for the authorization purpose).
3) I just need read only access of the data.
Please help me with this.
04-01-2022 10:42
04-01-2022 10:42
Hi @pawan.s
Welcome to the forums!
You'll need to reference your Client ID and Client Secret in your HTTP library to be able to make client calls to the Web API. If you're unsure how to implement the OAuth 2.0 spec in your application code, I recommend checking out our community resources for sample code.
Also, see our Getting Started guide to help you through the registration process and begin accessing user data.
04-03-2022 22:32
04-03-2022 22:32
Hi John,
Thank you so much for the answer, but My issue still stands. So, lets view it like this; there are two flow:-
1) I am a developer , I want my fitbit data to be shown in my own application so I went to dev.fitbit.com and got the client ID for my application, and followed the authorization guidelines to get the access token.
2) I am the Developer's friend and I want to use his application to see my fitbit data in his application and I am literate enough to only provide my fitbit sign in credentials. (I want answer for this flow).
The client ID you have mentioned is used to get access token after the USER grants the scope consent and is meant for single account only. Is there a way to get the access token / User health data by just using the fitbit lgoin?
04-03-2022 22:51 - edited 04-03-2022 22:57
04-03-2022 22:51 - edited 04-03-2022 22:57
@pawan.s - Yes same question, what is the user token of the person running the app?
Why is one even necessary when the user is accessing his own data, by giving his own userid, by default "-", in the URL, indicating he is already known and authorized and not trying to access the data of someone else on the fitbit.com site?
So by specifying "-" in the URL the app can't be accessing anybody else's data.
Author | ch, passion for improvement.