How does validated data work and what vendors and endpoints support validated data?
Validated data is device generated data. For supported apps and endpoints except for Fitbit, records will already be marked as validated if they are device generated. A validated record will either be completely device generated or non-validated if any value was changed as a result of user intervention. For a list of apps and endpoints that support validated data, please see our Validated Endpoints per App support article.
For Fitbit, a request must be made to Validic to enable validated data for a specific organization. This will prevent non-validated data from being returned by the Routine endpoint for Fitbit. Water data that is logged manually via the Fitbit mobile app or web portal will be included with validated Routine data. User updates to these records will not invalidate the routine records as with other vendors. The original validated record will be the only data returned. Other endpoints will still return validated and non-validated Fitbit data.
Validated Data Request Example
GET https://api.validic.com/v1/organizations/{ORGANIZATION_ID}/routine.json?access_token={ACCESS_TOKEN}
Each record in the response will contain a field labeled "validated" that will be set to either "true" or "false". If the field is set to "true", the record was generated by a device. If the field is set to "false", we cannot verify if it is device generated data or if it was manually entered data.
Validated Data Response Example
{
"summary":{
...
}
},
"routine":[
{
"_id":"5592baa295f8f742a501a11f",
"timestamp":"2015-06-30T16:00:00+00:00",
"utc_offset":"+08:00",
"steps":191.0,
"calories_burned":54.0,
"distance":141.92,
"floors":null,
"elevation":null,
"source":"fitbit",
"source_name":"Fitbit",
"last_updated":"2015-06-30T16:25:26+00:00",
"user_id":"54f713479fa53eb448000304",
"validated":true
}
]
}