The activityCalories data is incorrect when using the "Get Daily Activity Summary" API.

[Pratik_19]

We are encountering discrepancies while fetching data using the following API endpoint: https://api.fitbit.com/1/user/-/activities/date/${date}.json Observations: activityCalories Value Anomaly: The activityCalories value appears to be excessively high, even exceeding the sum of caloriesOut and caloriesBMR. Inconsistent Field Naming: The field caloriesBmr is now being returned instead of caloriesBMR, which differs from the documented naming convention (caloriesBMR). Other Potential Issues: There might be additional changes or issues, but they have not been fully identified yet. Request: Please provide documentation on the recent changes, or take the necessary actions to address these issues.

[Pratik_19]

We are encountering discrepancies while fetching data using the following API endpoint:

https://api.fitbit.com/1/user/-/activities/date/${date}.json

Observations:
activityCalories Value Anomaly:

The activityCalories value appears to be excessively high, even exceeding the sum of caloriesOut and caloriesBMR.
Inconsistent Field Naming:

The field caloriesBmr is now being returned instead of caloriesBMR, which differs from the documented naming convention (caloriesBMR).
Other Potential Issues:

There might be additional changes or issues, but they have not been fully identified yet.
Request:
Please provide documentation on the recent changes, or take the necessary actions to address these issues.

[mm-dev-wearabes]

We have seen this too.  The data change was first noticed on Friday, 8/30/2024 when calls to parse the data began failing on not finding the caloriesBMR field.  Only when we examined the payloads did we notice the mixed-case change.

A public API like this cannot (should not) change a field like that and not expect major disruptions in the usage of the API.  All doc still has caloriesBMR as the field to read.  What's even stranger is that not all users have this issue.  Some user data comes back with caloriesBMR still.

[aarondavidson]

I concur, seeing these same issues and having users suddenly complain that the reported values synced to our app are too high.  I note that  your status page acknowledges there's an issue since teusday:

"Some users may notice data discrepancies or syncing issues between 3P apps and Fitbit. Our team is currently investigating the root cause of the issue."

Can someone from fitbit give us any guidance on timelines or steps to mitigate if these JSON values have semantically changed?

[Gordon-C]

Hi everyone,

I believe this is a known issue and we are working on a fix.   

[joshua.a]

Hello Gordon, 

Any update on where this issues stands? 

Thanks

[joshua.a]

Hello @Gordon-C. I see that the API service disruption status that aarondavidson referenced above has been resolved on the status dashboard; however, a few of our users started reporting similar issues in early September and have continued to experience problems even after the service disruption was resolved on the status dashboard late last week. In our case, the step counts users see in their Fitbit apps are not aligning with the step counts we are receiving--our step counts are anywhere between 1,000 to 10,000 steps lower than the user's with no obvious explanation for the missing data.

Any insight into what the underlying issue could be? Do you think it's related to the service disruption reported on previously? 

[John-S]

We are having the same issues where the DailySummaries `steps` are LESS than what is in the ActivityTimeSeries calls and what is being shown in the users App. We've always (8 years) used the DailySummaries.

Any idea why this is happening?