Discrepancy in food log on website versus API

[awoulfe]

I recently noticed a disceprancy in data provided on the website that is not being sent in the API where the foodlogs are concerned. I am not receiving the nutritional values in the XML for some food items; however, this information is available on the site. Why is this not available through the API? These are public food items.

Here is the item on the website:

Here is the XML

-<apiFoodLogImplV1>

<isFavorite>false</isFavorite>

<logDate>2014-05-28</logDate>

<logId>912098249</logId>

-<loggedFood>

<accessLevel>PUBLIC</accessLevel>

<amount>1</amount>

<brand>Quaker</brand>

<calories>290</calories>

<foodId>14731101</foodId>

<locale>en_US</locale>

<mealTypeId>3</mealTypeId>

<name>Real Medleys Cherry Pistachio Oatmeal +</name>

-<unit>

<id>228</id>

<name>package</name>

<plural>packages</plural>

</unit>

-<units>

<long>228</long>

<long>226</long>

<long>180</long>

<long>147</long>

<long>389</long>

</units>

</loggedFood>

</apiFoodLogImplV1>

[SunsetRunner · Accepted solution]

We include full nutrition information for the private foods of the user (that he creates either via the API or Fitbit), and only a subset for the foods from the public Food DB due to the licensing considerations.