09-04-2024 01:52
09-04-2024 01:52
Some time starting around UTC 29 August 2024, the response received for daily activity summary's activeScore is returning something like this:
{
"goals" : {
...
},
"summary" : {
...
"activeScore" : "-1",
},
}
Previously, and as seen in the sample response in documentation (https://dev.fitbit.com/build/reference/web-api/activity/get-daily-activity-summary/), it used to return activeScore as a Number, not String - something like this:
{
"goals" : {
...
},
"summary" : {
...
"activeScore" : -1,
},
}
Is this an intentional change, or a bug?
09-04-2024 09:28
09-04-2024 09:28
I reported issue for issue in the API response.
https://community.fitbit.com/t5/Web-API-Development/The-activityCalories-data-is-incorrect-when-usin...
Best Answer09-04-2024 10:29
09-04-2024 10:29
I'm experiencing this too, as well as something potentially related in heart rate zone minutes in the get activities log response: where I'd expect a positive number or zero, I sometimes get the string "-1".
For example:
{
"activities": [
{
[...]
"heartRateZones": [
{
"minutes": "-1",
"caloriesOut": 0.0,
"name": "Out of Range",
"min": 30,
"max": 220,
"enabled": true
},
[...]
],
"customHeartRateZones": [],
"activeZoneMinutes": {
"totalMinutes": 15,
"minutesInHeartRateZones": [
{
"minutes": "-1",
"zoneName": "Out of Range",
"order": 0,
"type": "OUT_OF_ZONE",
"minuteMultiplier": 0
},
[...]
]
}
}
]
}According to my logs, this started sometime on Aug 28th 2024.
Best Answer09-09-2024 11:13
Fitbit Developers oversee the SDK and API forums. We're here to answer questions about Fitbit developer tools, assist with projects, and make sure your voice is heard by the development team.
09-09-2024 11:13
Hi @hi_SG
Thank you for reporting this problem. I can reproduce it and will send a ticket to engineering.
Best Answer09-09-2024 18:44
09-09-2024 18:44
Thanks Gordon.
We're facing another issue today with invalid format for activitycalories and caloriesbmr, both of which are now also returning a string instead of a number. I'm not sure if there will be any other fields with similar issues. Could we ensure the team resolves the format for all of the fields? Thanks!