We've started getting 404 when hitting https://api.fitbit.com/oauth2/introspect after OAuth authentication. This code has been working for months, so I'm wondering whether something is happening on Fitbit's end.
Answered! Go to the 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.
Hi @dataperson...Yes, the Introspect v. 1.0 endpoint was disabled as described in this post.
Please use the new version of the endpoint, /1.1/oauth2/introspect.
Best AnswerThat endpoint is deprecated, so perhaps Fitbit just killed it (https://dev.fitbit.com/build/reference/web-api/introspect-v1/). Here is the updated endpoint: https://dev.fitbit.com/build/reference/web-api/oauth2/#retrieve-state-of-tokens
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.
Hi @platejoy. I sent you a PM requesting feedback on our announcement process. Please respond when you have a chance.
Best AnswerWe are also recently seeing issues with these API's were they taken down?
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.
Hi @dataperson...Yes, the Introspect v. 1.0 endpoint was disabled as described in this post.
Please use the new version of the endpoint, /1.1/oauth2/introspect.
Best Answer