We are having the same problem with the rest API. We’ve made no code changes and all of a sudden the only response we get is 403

Hi ​@jm-apex, thanks for reaching out and providing the error message and screenshot! 

I sent this topic over to our API team, and they noticed that you have Bearer <token> in the header parameter, this should just be <token> without the Bearer part. Hope that helps! 

Hi ​@VFPhoto, thanks for chiming in here! 

Are you getting any specific error message similar to what jm-apex shared in their original post? 

Possible causes of 403 errors is if the token doesn't have the correct scopes enabled (e.g. the /v1/me endpoint requires current_user:read for the token. But this would show a more descriptive error than "Invalid token" in the body of the 403 (e.g. Invalid scopes...). It's hard to sure without the error message, so please let me know at your earliest convenience.