02-14-2015 08:41
02-14-2015 08:41
Heyhey,
I understand from the doc's page "API get user info" that public profile data requests do not require an OAuth-token.
However, when I use the API explorer with "Get User Info" from my own profile (everything public there!) with "No Auth", I get a bad request, i.e. OAuth error (see screen shot below).
Am I doing something wrong or can the public profile data simply not be accessed without OAuth?
I'd be very happy about any hint here 🙂
Answered! Go to the Best Answer.
03-04-2015 10:52
03-04-2015 10:52
Get User Info will return public profile data when only signed with client credentials. You would only pass your consumer key without a user access token and sign the request with your consumer secret without a user access token secret.
This probably won't work in the API Explorer, as I think that app requires a user authorization in order to sign the request at all.
However, client-only access to the FItbit API is likely to be removed in the future and relying on this functionality is strongly discouraged. You should only ever make requests to the Fitbit API on behalf of an authorized user.
03-03-2015 12:35
03-03-2015 12:35
03-04-2015 10:52
03-04-2015 10:52
Get User Info will return public profile data when only signed with client credentials. You would only pass your consumer key without a user access token and sign the request with your consumer secret without a user access token secret.
This probably won't work in the API Explorer, as I think that app requires a user authorization in order to sign the request at all.
However, client-only access to the FItbit API is likely to be removed in the future and relying on this functionality is strongly discouraged. You should only ever make requests to the Fitbit API on behalf of an authorized user.