API vs Application data mismatch

[amirrez]

We're using the following Fitbit Web API endpoints to retrieve 1-minute resolution data for calories, steps, and distance:

/1/user/-/activities/calories/date/[DATE]/1d/1min.json

/1/user/-/activities/steps/date/[DATE]/1d/1min.json

/1/user/-/activities/distance/date/[DATE]/1d/1min.json

However, the data returned by the API does not match what the user sees in their Fitbit mobile app for the same day.

We are not passing any timezone parameters, assuming that the default behavior is to return data in the user’s local timezone.

Any insights, suggestions, or guidance would be greatly appreciated.

Thanks in advance!

[GordonFitbit]

Hi @amirrez 

I will need to collect some detailed information about the user to troubleshoot this problem.  I will send you a private message through Issue Tracker.

[wefitter]

We are experiencing similar data mismatches between the data in the FitBit app and the data we pull from the API. Suggestions?

[GordonFitbit]

Hi @wefitter 

Would you please provide the endpoints that you're receiving the mismatch data, and what mobile device you are using?

Thanks!

Gordon

[wefitter]

The endpoints are: 

/1/user/-/activities/steps/date/{start-date}/{end-date}.json

 We experience the mismatches for several mobile devices, typically Android phone, sometimes Health Connect connected to Fitbit ...

Hope you can provide us with some insights and/or solutions.

Kind regards, GJ