...
This article pertains to:
Status | |
---|---|
|
...
|
...
Why am I unable to connect my Fitbit account to my App Marketplace when I only wanted to authorize my app to access my Fitbit device/settings and activity/exercise data?
...
Please note that unlike the old version that they had, ALL SCOPES are unchecked by default when the scope selection screen is loaded. A new selectionoption, "Allow All" Scope , will check all scopes displayed on the Fitbit Auth page for ease of use.
The user's choices on which scopes/data points are shared would have the following effects:
Validic requires that AT LEAST the “profile” and “Fitbit Devices and Settings”scopes are scope is allowed (this establishes the user’s timezone, OAuth identify for correct mapping, and frequency of data pull)
Depending on what scopes the user selects, certain data may not be captured by Validic. Below are the scopes that Validic currently supports. Data for any scopes not listed below that Fitbit may offer is not currently available in the Validic Inform API.
If a user does not authorize Profile, no data will be captured. This is a required scope.
If a user does not authorize Food and Water Logs, no Nutrition record will be writtenretrieved.
If a user does not authorize Activity and Exercise, no Summary data or Workout activities will be capturedretrieved.
If a user does not authorize Weight, no Measurement records will be writtenretrieved.
If a user does not authorize Sleep, no Sleep records will be writtenretrieved.
If a user does not authorize Fitbit Devices and Settings, data Heart rate, heart rate fields will not be included in Workout and Summary records and heart rate variability fields will not be retrieved included in realtimeSummary records.
If a user does not authorize Heart Breathing rate, no Measurement or Summary records will be written and heart rate fields in Workout records will not be includedrespiration rate fields will not be included in Summary records.
If a user does not authorize Oxygen saturation (SpO2), SpO2 fields will not be included in Summary records.
If a user does not authorize Temperature, body temperature fields will not be included in Summary records.
We highly recommend that users authorize Fitbit Devices and Settings for future compatibility.