10-09-2024 08:14
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

10-09-2024 08:14
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Hi there,
The last week we've had several instances where our application endpoint got disabled.
There's no reported issue at the Fitbit Status Dashboard https://status.fitbit.com/
Lots of SocketExceptions in the stats. Not sure if that's the cause or result of the disabled endpoint.
We can enable it, but we'd like to prevent it from getting disabled.
When and why are endpoints disabled automatically?
10-09-2024 12:47 - edited 10-09-2024 12:48
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

10-09-2024 12:47 - edited 10-09-2024 12:48
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Hey Len - Here's a reason we encountered a few years.
We had a problem where our endpoint would be deactivated every hour to a couple of hours, even with a 100% success on receiving notifications. Long story short, we traced it to a Fitbit server pinging our endpoint address, not getting a response (because we had recently turned off responding to pings), and then it eventually thinking our endpoint was no longer up and disabling us.
I'm not sure that it's still applicable today or not, and we haven't turned off ping for that subnet to test.
- Jay

10-14-2024 11:04
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post



10-14-2024 11:04
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Hi @Len3
We list the reasons that subscribers will become disabled in the documentation.
Senior Technical Solutions Consultant
Fitbit Partner Engineering & Web API Support | Google

