This article pertains to: INFORM (V2)
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?
How does a user’s authorization of certain types of data on the Fitbit OAuth page affect what information is made available through the API?
The Fitbit authorization page allows the user to pick particular data points (scopes) to allow access to through Validic. A user may choose to share ONLY certain scopes, but we do recommend your review of the outline below on specific scopes that are required to properly establish the connection as well as what data is available based on the scopes allowed by a user. If users do not select the appropriate scopes, you will not receive any data even though the user shows as connected.
Please note that unlike the old version that they had, ALL SCOPES are unchecked. A new selection, "Allow All" Scope will check all scopes displayed on the Fitbit Auth page.
The user's choices on which data points are shared would have the following effects:
Validic requires that AT LEAST the “profile” 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.
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 retrieved.
If a user does not authorize Activity and Exercise, no Summary data or Workout activities will be retrieved.
If a user does not authorize Weight, no Measurement records will be retrieved.
If a user does not authorize Sleep, no Sleep records will be retrieved.
If a user does not authorize Heart rate, heart rate fields will not be included in Workout and Summary records.
We highly recommend that users authorize Fitbit Devices and Settings for future compatibility.