Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Validic requires that AT LEAST the “profile” scope is allowed (this establishes the user’s timezone and OAuth identify for correct mapping of records)

  • Depending on what scopes the user deselects, certain data may not be captured by Validic.

    • ​If a user does not authorize Profile, authorization will fail and no data will be captured.

    • If a user does not authorize Food and Water Logs, a routine record will still be written, but no ‘Water’ data will be captured. In addition, No Nutrition record will be written.

    • If a user does not authorize Activity and Exercise no Routine data or Fitness activities will be captured.

    • If a user does not authorize Weight, no Weight records will be written.

    • If a user does not authorize Sleep, no Sleep records will be written.

    • If a user does not authorize Fitbit Devices and Settings, no user device information will be written on the Profile.json endpoint.

    • If a user does not authorize Heartrate, no Biometrics records will be written and certain fitness fields will be null.

    • If a user does not authorize Settings, data will not be retrieved in realtime.

...

Status
colourBlue
titleValidic Legacy API (V1)
Status
colourGreen
titleInform (v2)