11-11-2015 21:50
11-11-2015 21:50
Hello there,
Can someone answer me? I see that the heartrate time series api has two types of ways to request :
GET https://api.fitbit.com/1/user/[user-id]/activities/heart/date/[date]/[period].json
GET https://api.fitbit.com/1/user/[user-id]/activities/heart/date/[base-date]/[end-date].json
In both the ways when I request for my past data ( anything other than the current day ) I don't seem to get the HeartRateZones with minutes.
Example Response :
"heartRateZones": [ { "max": 94, "min": 30, "name": "Out of Range" }
....
]
When I request for the current day (today or with exact date) I get the zones with minutes. Am I missing somethinhg? Do I need to make any Application level changes (manage apps) ? Please suggest some solution for this !
11-16-2015 13:19
11-16-2015 13:19
This seems to be working for me. I tried:
https://api.fitbit.com/1/user/-/activities/heart/date/today1d.json
https://api.fitbit.com/1/user/-/activities/heart/date/2015-10-16/1d.json (a month ago)
Do you have heart rate data from a device on the days in the past?
11-19-2015 21:37
11-19-2015 21:37
Yes I do. I am sure of whats wrong
11-20-2015 10:37
11-20-2015 10:37
Capture your API request (with a tool like Runscope) and share it with us. Be sure to redact your access token before posting.
11-21-2015 06:09
11-21-2015 06:09
I think that the heart rate intraseries is inherently broken anyway. I've used it in a web application and some of the data was truly baffling, such as a mid-50s male having a heart rate over 190 constantly, every day at the same time. We can't use the exertion details because of that, so we just use average resting heart rate.
11-23-2015 10:42
11-23-2015 10:42
That does sound unusual, but the time series is not inherently broken. Perhaps that user has a bad device.