Hi! We have an app that integrates with the Fitbit api, and we rely on webhooks for data updates.
We noted that we are missing sleep data for a certain user for several (!) days over the past two weeks (dates with disruptions were December 15, 19, 26, 30, and 31).
* We know that the customer may be syncing their Fitbit data with delays.
* The user sleep data for the abovementioned dates is currently available from the Ftbit api, but our app is not aware of it.
* We do monitor webhook inflow, and we are solidly sure we have processed all the webhooks that reached us within the past two weeks.
= This makes us think that some of the webhooks were not sent to us, or data was not available when we were processing the webhooks.
Questions:
(1) Are webhooks sent for updates covering dates in the past?
(2) Is there any way to see the history of webhooks sent for some user?
(3) What is the best practice you suggest to protect against potentially missing webhooks?
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