04-19-2016 10:42
04-19-2016 10:42
I logged into dev.fitbit.com, click on "Manage Your Apps", clicked on my app. I only see:
Answered! Go to the Best Answer.
04-19-2016 12:36 - edited 04-19-2016 12:37
04-19-2016 12:36 - edited 04-19-2016 12:37
OAuth 1.0a support was removed on April 12, 2016. Applications using OAuth 1.0a prior to April 12th can continue to use it until August 1, 2016, when it will be removed permanently. See https://community.fitbit.com/t5/Web-API/OAuth-1-0a-removal-update/m-p/1272107#U1272107 .
04-19-2016 12:36 - edited 04-19-2016 12:37
04-19-2016 12:36 - edited 04-19-2016 12:37
OAuth 1.0a support was removed on April 12, 2016. Applications using OAuth 1.0a prior to April 12th can continue to use it until August 1, 2016, when it will be removed permanently. See https://community.fitbit.com/t5/Web-API/OAuth-1-0a-removal-update/m-p/1272107#U1272107 .
04-19-2016 13:00
04-19-2016 13:00
OK thank you!
06-02-2016 16:42
06-02-2016 16:42
I'm still not able to resolve this - I looked through the documentation, but I haven't been able to figure out how to obtain a consumer key. I've been using python libraries for the FitBit API that specify compatibility with OAuth 2.0, and they all use consumer keys. I looked through the documentation but I wasn't able to find an explanation of the lack of a consumer key. Could you go into more detail about the change?
06-02-2016 17:52
06-02-2016 17:52
Resolved!
06-17-2016 00:45
06-17-2016 00:45
How did you solve it? I need the fitbit key and the fitbit secret but all i get when i register my app on Fitbit is an
OAuth 2.0 Client ID and a Client Secret and they don't seem to work.
06-17-2016 10:46
06-17-2016 10:46
@JeremiahFitbit wrote:
OAuth 1.0a support was removed on April 12, 2016. Applications using OAuth 1.0a prior to April 12th can continue to use it until August 1, 2016, when it will be removed permanently. See https://community.fitbit.com/t5/Web-API/OAuth-1-0a-removal-update/m-p/1272107#U1272107 .
@AntonyM You should be using OAuth 2.0, see Jeremiah's post.