Summary: The "activities/tracker/calories" resource on the Get Time Series endpoint reported "estimated calories" for some users when it should have only reported BMR calories on days when the user had no tracker data.
Details: Fitbit’s calorie estimation feature estimates the number of calories a user likely burned in a day based on their previous days’ trend in the absence of actual tracker data. The first time a user syncs a tracker with activity data on a day or logs an activity on a day, the standard calorie counting method is used instead of the estimate.
The "activities/tracker/calories” time series resource should only report calories burned as measured by a Fitbit tracker. However, we identified that Fitbit’s calorie estimation feature was returning data on this endpoint. This means that your application may have received incorrect calorie values prior to Monday, February 23, 2015, when the issue was fixed.
Scope: The calorie estimation feature was deprecated in 2013 and was permanently disabled for all users on Monday, February 23, 2015. Approximately half of Fitbit users had this feature enabled prior to it being disabled. More recent Fitbit users were less likely to have had this feature enabled.
Resolution: If needed, you should re-request the "activities/tracker/calories" time series for correct data.
Owners of applications that accessed this endpoint and resource between February 11–18th were emailed on February 23, 2015 about this issue. If you have questions about a specific user’s data, please email api at fitbit.com, otherwise please respond below.
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.
Best Answer
