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

OAuth 2 expired_token error change

ANSWERED

Hi,

implementing token refreshing detection, hitting some issues.

 

Your spec says the error returned is:

{"errors": [{"errorType": "oauth", "fieldName": "access_token", "message": "Access token invalid or expired: {token}"}]}

 

But what I get back from the API is:

{"errors":[{"errorType":"expired_token","message":"Access token expired: {token}. Visit https://dev.fitbit.com/docs/oauth2 for more information on the Fitbit Web API authorization process."}],"success":false}

 

What should I check for? Will it change in the future?

 

Moderator edit: moved to own topic

Best Answer
0 Votes
1 BEST ANSWER

Accepted Solutions

Hi,

 

See https://community.fitbit.com/t5/Web-API/OAuth-2-0-error-changes/td-p/1138662. We inadvertently released backwards-incompatible changes to our error handling without appropriate notice. Apologies for the incovenience. 

View best answer in original post

Best Answer
0 Votes
1 REPLY 1

Hi,

 

See https://community.fitbit.com/t5/Web-API/OAuth-2-0-error-changes/td-p/1138662. We inadvertently released backwards-incompatible changes to our error handling without appropriate notice. Apologies for the incovenience. 

Best Answer
0 Votes