I logged into dev.fitbit.com, click on "Manage Your Apps", clicked on my app. I only see:
Answered! Go to the Best Answer.
Best Answer
Fitbit Developers oversee the SDK and API forums. We're here to answer questions about Fitbit developer tools, assist with projects, and make sure your voice is heard by the development team.
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 .
Best Answer
Fitbit Developers oversee the SDK and API forums. We're here to answer questions about Fitbit developer tools, assist with projects, and make sure your voice is heard by the development team.
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 .
Best AnswerI'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?
Best AnswerHow 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.
Community Moderator Alumni are previous members of the Moderation Team, which ensures conversations are friendly, factual, and on-topic. Moderators are here to answer questions, escalate bugs, and make sure your voice is heard by the larger Fitbit team. Learn more
@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.
Best Answer