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

Get Daily Activity Summary Endpoint Issues

Hi, 

Using the Get Daily Activity Summary endpoint to check steps hourly during the day has starting returning incorrect data.  If the endpoint is called before midnight the returned value is users steps for the day.  This is the expected behavior.   When the endpoint is called shortly after the following day, the steps returned are the same as what was correctly returned by the previous call.  This is unexpected.   The second call should not return yesterday's total but only today's.  Subsequent calls do correctly return the users steps for that day.  

Is there a reason for this API change?

Best Answer
3 REPLIES 3

Hi @scoon 

  • When did this problem begin to occur?
  • How frequently does this occur?   Does it occur for all users?  Does it occur every day?
  • Do you know if you reside in the same time zone as the users who's data you are querying?  
  • Do you know if the user has synced their device between midnight and the time that you query their data?   If you requested the "settings" scope, then you can call Get Devices to find out.
  • Do you know if the user syncs their device after midnight between the first (yesterday's step count) and second (today's step count) time that you query their data?

 

Gordon Crenshaw
Senior Technical Solutions Consultant
Fitbit Partner Engineering & Web API Support | Google
Best Answer
0 Votes

Hi @Gordon-C ,

We are also experiencing this issue.

  1.  At the time change for daylight savings, so Nov 3rd.
  2. Every night, for all users
  3.  No but we've had this code for years without issue
  4. We don't have that scope
  5. The data comes in as {steps: step data from yesterday, minutes: 0, distance: 0} ie {steps: 16400, minutes: 0, distance: 0}
Best Answer
0 Votes

Hi @scoon and @Hills123 

We found a problem where the step data was being carried over to the next day until the user first synced.  We have fixed this problem.   Would you please check to see if the problem still exists on your end?

Gordon Crenshaw
Senior Technical Solutions Consultant
Fitbit Partner Engineering & Web API Support | Google
Best Answer