03-28-2017 14:03
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

03-28-2017 14:03
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Hi Fitbit Team,
We are attempting to disable the API for our Fitbit Account to help us catch up on the processing of our previously received workouts. However, when I go to the Edit Applications page for our account, uncheck the "Enabled" box, and click Save: I receive a "Sorry...It's not you. It's Us." error page. Please see the screenshots. Is there a workaround for this issue or can it be fixed?
Thanks,
Andrew Barr
abarr@thevitalitygroup.com

- Labels:
-
Subscriptions API
03-28-2017 15:14
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post



03-28-2017 15:14
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
@TVG_ It's currently being investigated.

03-28-2017
16:39
- last edited on
03-28-2017
16:54
by
AndrewFitbit
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

03-28-2017
16:39
- last edited on
03-28-2017
16:54
by
AndrewFitbit
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Do you have an ETA on resolution?

03-29-2017 14:04
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

03-29-2017 14:04
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Hi Andrew. We no longer have a need to disable our API connection.
However, we had an issue with one of our nodes that caused the API to auto-disable and now we are receiving the same error when we are trying to enable the API. We have fixed the node issue and now we really need to start receiving workouts again soon. Even if this issue is not yet resolved on your end, could you please re-enable our API connection on your side?
Thank you.

03-29-2017 16:30
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post



03-29-2017 16:30
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
You can try to to re-enable your subscriber now. There shouldn't be any issues.

03-29-2017 19:44
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

03-29-2017 19:44
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
I am still receiving the same error. I tried in a few different browsers. If possible, can you re-enable it from your side for now?

