# API errors / OAuth

**URL:** <https://discuss.dev.twitch.com/t/api-errors-oauth/50824>\
**Category:** API\
**Created:** [November 15, 2023, 12:29pm UTC](https://discuss.dev.twitch.com/t/api-errors-oauth/50824 "2023-11-15T12:29:23Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![DevMcGee](https://avatars.discourse-cdn.com/v4/letter/d/839c29/32.png) [@DevMcGee](https://discuss.dev.twitch.com/u/DevMcGee)\
**Post date:** [November 15, 2023, 12:29pm UTC](https://discuss.dev.twitch.com/t/api-errors-oauth/50824/1 "2023-11-15T12:29:23Z")

</div>

[https://id.twitch.tv/oauth2/token](https://id.twitch.tv/oauth2/token) 404 Not Found  
Makes authorizing and validating a bit inconvenient

---

<div class="post-metadata">

**Author:** ![BarryCarlyon](https://d3ovvz0v2ajtpu.cloudfront.net/user_avatar/discuss.dev.twitch.com/barrycarlyon/32/253_2.png) [@BarryCarlyon](https://discuss.dev.twitch.com/u/BarryCarlyon)\
**Post date:** [November 15, 2023, 12:31pm UTC](https://discuss.dev.twitch.com/t/api-errors-oauth/50824/2 "2023-11-15T12:31:02Z")

</div>

Everything looks ok to me here.

Are you GETting by accident?

My web flows/tooling is ok  
And `twitch token` in the CLI is working for a client credentials generation

---

<div class="post-metadata">

**Author:** ![DevMcGee](https://avatars.discourse-cdn.com/v4/letter/d/839c29/32.png) [@DevMcGee](https://discuss.dev.twitch.com/u/DevMcGee)\
**Post date:** [November 15, 2023, 12:32pm UTC](https://discuss.dev.twitch.com/t/api-errors-oauth/50824/3 "2023-11-15T12:32:23Z")

</div>

No. Everything was working yesterday and I haven’t changed anything.

---

<div class="post-metadata">

**Author:** ![DevMcGee](https://avatars.discourse-cdn.com/v4/letter/d/839c29/32.png) [@DevMcGee](https://discuss.dev.twitch.com/u/DevMcGee)\
**Post date:** [November 15, 2023, 6:55pm UTC](https://discuss.dev.twitch.com/t/api-errors-oauth/50824/4 "2023-11-15T18:55:42Z")

</div>

Hi,

Apparently I did introduce a bug on my testing system which resulted in the request being sent improperly (yes, as a GET). At the same time, my production system got disconnected and was inexplicably requiring a new token. I’ve never seen that before, so I reasonably but incorrectly assumed these were connected.

I fixed the bug in my test code and got that working, and I restarted the production instance and it’s working happily now (with the old token).

---

<div class="post-metadata">

**Author:** ![system](https://d2opxh93rbxzdn.cloudfront.net/original/2X/0/05909729875cce3b53e59d5561c4d23bb14948fc.png) [@system](https://discuss.dev.twitch.com/u/system)\
**Post date:** [December 15, 2023, 6:56pm UTC](https://discuss.dev.twitch.com/t/api-errors-oauth/50824/5 "2023-12-15T18:56:12Z")

</div>

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