Fitbit Intra Day Heart Rate Data Missing since July

[afolarin]

Hi, 

I wonder if I can find out if there have been any changes to the WebAPI recently? We seemingly encountered an issue around the 20th of July, we'd been collecting the data fine till this point.

The problem: We are having missing intraday heart rate and calories data from the Fitbit Web API for many users. The data for intraday-steps, sleep and profile are complete for the corresponding time points. Is there any reason we might expect this (the project has been collecting research data on a cohort of participants for 2years).

This was working fine till around 20th July 2020. And not all participant accounts are affected by this. Have there been any recent changes to the API call rate limits?

Additional Info: We have some failed refresh token requests for our client due to users changing passwords, as the exited the study, could the amount of failed requests somehow throttle the data collection from Fitbit Web API?

Any suggestions welcome and much appreciated.

[Gordon-C]

Hi @afolarin 

We have not changed anything with the APIs that would have affected intraday heart rate and calories data.  If you private message me a Fitbit user id that is affected, I can look into it.

Also, refresh tokens should not be related to user's changing their passwords.  However, if the user revoked access to your application, then the user would need to reconsent and you would need to obtain new access token and refresh tokens for the users.   

[participant4tes]

I'm facing the same issue. The data export from the Fitbit user dashboard and the API response both have missing heart rate data using the 'Personal' app type only for select users while others have all heart rate data available.

[dgfitch]

Same issue, we used to be able to grab URLs from the API like: https://api.fitbit.com/1/user/-/activities/tracker/heart/date/2019-08-06/1d/1min.json

But this is throwing an HTTP 400.