7

I have followed the documentation and used explicit OAuth 2.0 flow for access_token generation.

And I have gone through all 4 steps defined under explicit OAuth 2.0 flow with scope=no_expiry. Then I got the access_token.

When I am using applicationKey and access_token for fetch data through Stack Exchange API, I am getting following error :

{
     "error_id": 403,
     "error_message": "`key` is not valid for passed `access_token`, token notfound.",
     "error_name": "access_denied"
}

I initially thought that there is something wrong with applicationKey. Then I found that using same applicationKey (used for access_token generation) in request are working fine for other API Methods where access_token is not required.

  • Did you ever get this sorted? I'm having the same problem. – RareNCool Jan 28 '16 at 16:32
2

In my particular case, I somehow managed to append % character to the end of the access_token. There should be no % character at the end of the access_token.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .