Issue with oauth/token endpoint

I’ve been using the Authentication system for a few weeks now with no issue.

Last night Sunday 21st May however I started to get Bad Requests from the kraken/oauth/token endpoint. However the error doesn’t make sense as I believe I am supplying a client ID

REQUEST as taken from fiddler

POST https://api.twitch.tv/kraken/oauth/token HTTP/1.1
Accept: application/vnd.twitchtv.v5+json
Content-Type: application/x-www-form-urlencoded
Host: api.twitch.tv
Content-Length: 220
Expect: 100-continue

client_id=59gf113hl2vbatr87bri9ajubnyqz0&client_secret={{SECRET}}&grant_type=authorization_code&redirect_uri=http%3A%2F%2Flocalhost%3A4141%2FAccountLinking%2FTwitch&code=v9ap6fraosku5j142mw4fp4sx71iva

RESPONSE as taken from fiddler

HTTP/1.1 400 Bad Request
Date: Mon, 22 May 2017 07:19:25 GMT
Content-Type: application/json
Content-Length: 71
Connection: keep-alive
Server: nginx
Access-Control-Allow-Origin: *
Cache-Control: no-cache, no-store, must-revalidate, private
Expires: 0
Pragma: no-cache
Twitch-Trace-Id: edc24a22aa15a7a1146d86ef37370972
X-Ctxlog-Logid: 1-592290fd-27f101df15b0f68934d2e76e
Timing-Allow-Origin: https://www.twitch.tv

{“error”:“Bad Request”,“status”:400,“message”:“No client id specified”}

Well that took far longer than expected and I finally found the change and didn’t even notice that I had done it.

It will teach me to just copy and paste, but I have been using /oauth/token… not oauth2/token…

Derp!

1 Like

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