Notifications sent before data is available via API

[amirrez]

When using Fitbit’s body/weight subscription notifications, we’re seeing cases where the webhook is delivered before the new data is actually available via the Web API.

Typical pattern:

- A new weight is logged.
- A body subscription notification is sent to our callback for that user/collection.
- Immediately after (and even several minutes after) receiving the notification, requests to the body/weight endpoint for that date return no new records.
- Hours later, the same request for the same user/date returns the new weight entry.

This seems similar to the issue described here:
https://community.fitbit.com/t5/Web-API-Development/Body-subscription-notifications-being-sent-befor...

I have also seen the above thread describing the same behavior, but no solution was posted there either.

We also observe a related issue with the foods summary API: sometimes the daily foods summary is returned with all figures as zero, even though there is clearly non-zero calorie intake logged for that day. Later, the same request for the same user/date returns the correct non-zero values.

What should I do with this?

[GordonFitbit]

Hi @amirrez 

This is true.  There is a problem with the body service where the weight and body fat data are not available immediately after the measurement has been taken.  Sometimes, it can take up to a day for the data to be available.  We are still investigating this problem.  When the problem is resolved, we will update everyone.