09-13-2018 12:48
09-13-2018 12:48
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.
09-17-2018 08:52
09-17-2018 08:52
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.
09-14-2018 13:13
09-14-2018 13:13
That 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
09-14-2018 15:37
09-14-2018 15:37
Hi @platejoy. I sent you a PM requesting feedback on our announcement process. Please respond when you have a chance.
09-17-2018 07:31
09-17-2018 07:31
We are also recently seeing issues with these API's were they taken down?
09-17-2018 08:52
09-17-2018 08:52
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.