Cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Starting today: https://api.fitbit.com/oauth2/introspect returning 404

ANSWERED

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.

Best Answer
0 Votes
1 BEST ANSWER

Accepted Solutions

Hi @dataperson...Yes, the Introspect v. 1.0 endpoint was disabled as described in this post.

 

https://community.fitbit.com/t5/Web-API-Development/Introspect-endpoint-ver-1-1-is-now-available/m-p...

 

Please use the new version of the endpoint, /1.1/oauth2/introspect.

Gordon Crenshaw
Senior Technical Solutions Consultant
Fitbit Partner Engineering & Web API Support | Google

View best answer in original post

Best Answer
0 Votes
4 REPLIES 4

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

Best Answer
0 Votes

Hi @platejoy.  I sent you a PM requesting feedback on our announcement process.  Please respond when you have a chance.

Gordon Crenshaw
Senior Technical Solutions Consultant
Fitbit Partner Engineering & Web API Support | Google
Best Answer
0 Votes

We are also recently seeing issues with these API's were they taken down?

Best Answer
0 Votes

Hi @dataperson...Yes, the Introspect v. 1.0 endpoint was disabled as described in this post.

 

https://community.fitbit.com/t5/Web-API-Development/Introspect-endpoint-ver-1-1-is-now-available/m-p...

 

Please use the new version of the endpoint, /1.1/oauth2/introspect.

Gordon Crenshaw
Senior Technical Solutions Consultant
Fitbit Partner Engineering & Web API Support | Google
Best Answer
0 Votes