06-06-2025 12:28
06-06-2025 12:28
As of a couple of days ago, I'm not able to access my Breathing Rate data. I get the message:
PERMISSION_DENIED - The caller does not have permission
Has something changed??
06-06-2025 19:57
06-06-2025 19:57
I'm getting the same issue. Not sure what happened?
06-07-2025 02:12
06-07-2025 02:12
It's weird. The breathing rate data is being gathered by my device, it's shown in the Fitbit app and online, but when I try to download the data from the Web interface, it's suddenly not available. Apparently I no longer have the required permissions to access that data.
Fitbit haven't changed the interface, at least not according to their website, so I'm at a loss as to what has happened here.
06-07-2025 13:07
06-07-2025 13:07
Yeah, I'm seeing the same.
It seems the Swagger API Explorer continues to work, once you authorize it: https://dev.fitbit.com/build/reference/web-api/explore/
I did try reauthorizing my app, but I continue to get `PERMISSION_DENIED`...
06-08-2025 20:06 - edited 06-08-2025 20:10
06-08-2025 20:06 - edited 06-08-2025 20:10
Having the same issue here.
Are we all using a Personal type application? As the Swagger API Explorer might continues to work if the issue only affects personal type applications but not server type applications that has been granted access to Intraday APIs.
I have also created a issue through google's issue tracker about the problem but simply received a response asking me to request for Intraday access, despite already stating that my client is a Personal type application. Added another comment clarifying my issue but have not received a response yet.
06-09-2025 00:29
06-09-2025 00:29
Yes, I'm using a Personal application. I'm using the Intraday by Date endpoint (/1/user/[user-id]/br/date/[date]/all.json), and the last time it worked was 4th June. Every day since then, it's "PERMISSION DENIED".
All rather annoying.
BTW, my phone app can still obtain and display some type of Breathing Data.
06-09-2025 19:19
06-09-2025 19:19
Hi there, I have same issue discussed here.
I got my own breathing_rate data at 5th June at last time.
In addition, I could not obtain my own heartrate variability for yesterday.
Python's "aiohttp" shows the API response:
* 403, message='Forbidden', url='~/hrv/date/{yyyy-mm-dd}/all.json'
* 403, message='Forbidden', url='~/br/date/{yyyy-mm-dd}/all.json'
06-27-2025 05:59
06-27-2025 05:59
Hey, did you hear back anything on this?
I see the issue is still ongoing for me...
06-27-2025 07:14
06-27-2025 07:14
06-27-2025 08:22
06-27-2025 08:22
That "PERMISSION_DENIED" error might be due to a recent Fitbit update, possibly related to app permissions or Premium access. Try updating the app, logging out and back in, and checking if Breathing Rate is still enabled in Health Metrics. If you’re not on Premium, that could also be the reason.
06-27-2025 08:26
06-27-2025 08:26
Thanks for continuing to look into it @mrchurch.
Hoping you can get it sorted out with their support. It's unfortunate about how long they're taking...
06-27-2025 08:49
06-27-2025 08:49
Hmm, this is via the WebAPI - I've actually tried re-authenticating my 'personal' web app (by asking for more permissions than what I had previously configured).
Or, are you saying to update the iOS/Android app? Not sure how that would help, but my iOS app is also up to date.
07-11-2025 10:11
07-11-2025 10:11
Thank you for your patience. If you're still having problem accessing your personal breathing rate data, please call the endpoint in your application, then provide me with your client ID. I'll take a look in our logs to see if I can determine the problem.
07-11-2025 10:37
07-11-2025 10:37
Hi everyone,
I have been able to reproduce the problem where owners of "personal" applications are not able to query their own breathing rate intraday data. I will be filing a bug to engineering today. When I receive an update/fix from engineering, I will post the update here.
Gordon
07-11-2025 10:44
07-11-2025 10:44
07-11-2025 11:42
07-11-2025 11:42
Thank you!
07-11-2025 11:44
07-11-2025 11:44
Also, please note that this seems to impact 2 endpoints:
07-20-2025 08:43
07-20-2025 08:43
The Fitbit Support team have finally been able to reproduce this error, as of 4 days ago. No indication of when a fix will be available, of course.
But I live in hope...