06-20-2016 15:39
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

06-20-2016 15:39
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Hi,
i am a product manager at Higi, a health engagement platfrom integrated with the fitbit API. For some reason, i am getting an Under Construction error when attempting to reauthorize my Fitbit in production. Any idea why this might be happening today? Can anyone help me investigate the issue?
06-20-2016 15:48
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post



06-20-2016 15:48
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
What is the URL where you are seeing this under construction message? This does not sound like a Fitbit page.

06-20-2016 15:54
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

06-20-2016 15:54
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
the error page itself is on our side. (higi.com) but I suspect its being caused by something on fitbit's end. We should be directed to the oauth page, but instead we're getting an error

06-20-2016 16:07
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post



06-20-2016 16:07
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Fitbit is not seeing any OAuth related issues at this time.
Do you see any errors in your application logs?
Are you using OAuth 1.0a or OAuth 2.0? Is this error before your application redirects to Fitbit's OAuth authorization page or after the consent?

06-20-2016 16:49
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

06-20-2016 16:49
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
This error is occuring before we get to fitbit's oAth page. We are using oAth 2.0

06-20-2016 18:12
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post



06-20-2016 18:12
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
With OAuth 2.0, there is no interaction with the Fitbit API prior to your application redirecting the user to the authorization page. Your app only needs to redirect the person to `https://www.fitbit.com/oauth2/authorize?...`.

06-21-2016 10:25
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

06-21-2016 10:25
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Hi Jeremiah,
My sincere apologies for the mix up. It turns out we are still on oAth 1.0. One of our developers mentioned that it would be supported up until August 1st. Can you confirm that we have this time period to complete the migration?

06-21-2016 11:21
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post



06-21-2016 11:21
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
OAuth 1.0a support has been extended until August 1st. (The original deadline was April 12th. Fitbit will not extend this deadline further.)

06-21-2016 12:24
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

06-21-2016 12:24
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Thanks for your help Jeremiah,
We will work on the migration asap.

