id.kick.com OAuth endpoints returning 404 — authorization_code flow completely broken

[richerd22]

Summary

The OAuth authorization subdomain (id.kick.com) is returning HTTP 404 on both the /oauth/authorize and /oauth/token endpoints, making it impossible to complete the Authorization Code flow for third-party apps.

Steps to Reproduce

1. Direct user to:
2. https://id.kick.com/oauth/authorize?client_id=<CLIENT_ID>&redirect_uri=http://localhost:3000&response_type=code&scope=channel:update
3. 2. Browser returns: HTTP ERROR 404 — "This id.kick.com page can't be found"

Expected Behavior

OAuth consent screen is presented so the user can authorize the app.

Actual Behavior

id.kick.com server responds but returns 404 on all OAuth paths:

• GET /oauth/authorize → 404
• • POST /oauth/token → 404

Timeline

• Sept 19 2026: id.kick.com completely unreachable (connection timeout)
• • Sept 20-21 2026: Server responds but all OAuth routes return 404

Environment

• App Client ID: 01M2WEYN058CXSA5EQB2QATV8M
• • Scope: channel:update
• • • Grant type: authorization_code
• • • • Redirect URI: http://localhost:3000

Impact

All third-party apps using Authorization Code flow are blocked. The channel:update scope for automated stream title updates is inaccessible. Kick support directed to this repo when contacted via email.

Notes

• api.kick.com appears functional — issue is isolated to the auth subdomain
• • client_credentials endpoint also on id.kick.com and likely also broken

[maiconcarraro]

review the required query parameter for the path, see docs: https://docs.kick.com/getting-started/generating-tokens-oauth2-flow#authorization-endpoint

for example state is missing, it's an old issue that they don't have a good error page feedback, but the oAuth is working currently if you pass all.