Cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Food item nutritional values inconsistency

Hi Team,

 

We have received a report from one of our client about a Food item data returning different nutritional values ( Fat / Carbs / Sodium / Protein ) than what is being shown in the Fitbit user dashboard. See data sample below;

 

 

"foods":[
            {
                "isFavorite":false,
                "logDate":"2015-08-26",
                "logId":3251576737,
                "loggedFood":{
                    "accessLevel":"PUBLIC",
                    "amount":1,
                    "brand":"",
                    "calories":133,
                    "foodId":82269,
                    "locale":"en_US",
                    "mealTypeId":1,
                    "name":"Banana Pudding",
                    "unit":{
                        "id":304,
                        "name":"serving",
                        "plural":"servings"
                    },
                    "units":[
                        304,
                        69,
                        251,
                        91,
                        256,
                        279,
                        226,
                        180,
                        147,
                        389
                    ]
                },
                "nutritionalValues":{
                    "calories":133,
                    "carbs":19.5,
                    "fat":4,
                    "fiber":3,
                    "protein":2.5,
                    "sodium":141.5
                }
            }

 

 

See corresponding Food item in the dashboard below;

 

fitbitnutrition.png

 

Please let us know if there is anything we're missing or this is a known issue and if you require further information. Looking forward for your assistance.

 

Best,

Mark Salcedo

Best Answer
0 Votes
1 REPLY 1

The food logging section of the Fitbit Web app is one that hasn't been updated to use the Fitbit API. My hunch is that the API is correct and that the Web app's logic is outdated. I have sent this to the engineering team responsible for this feature to investigate.

Best Answer
0 Votes