#1

Hi,
I am having a really hard time getting into the Twitter API because of a possible internal problem in it. I am trying to invalidate a bearer token using invalidate_token.json (in OAUTH2, NOT OAUTH1), and it throws me… a 404 Not Found.

I have never seen such an issue with any public API before… can someone help me?

With frustrations and regards, Omer Shamai.

1 Like
#2

What’s the exact endpoint you’re calling here, please?

#3

@andypiper

https://api.twitter.com/1.1/oauth2/invalidate_token.json

the exact endpoint given on the API reference.

#4

I also have seen this when using the exact endpoint in the documentation https://api.twitter.com/1.1/oauth2/invalidate_token.json. After playing around with the endpoint I was able to get passed a 404 by changing the endpoint to https://api.twitter.com/oauth2/invalidate_token, however I now get twitter error code 348 ‘Client application is not permitted to to invalidate this token.’

#5

Yeah, pretty much the same @nickhyland13

I think something is terribly broken…

#6

I believe there may be a documentation issue with the path of the endpoint, however I am not sure of the cause of the 348 error immediately.

#7

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.