Skip to content

OAuth Authorization Not Working - 404 Error #40

Description

@caenvibe

I'm trying to integrate Kick OAuth for my application, but the authorization endpoint is not working.
The URL I used:

https://id.kick.com/oauth2/authorize?client_id=MY_CLIENT_ID&redirect_uri=http://localhost:5000/callback&response_type=code

When I try to access this URL, I get a 404 error (Page Not Found).

Steps to Reproduce

  1. Created an app in Kick Developer portal.
  2. Added http://localhost:5000/callback as my redirect URI.
  3. Used the authorization URL above.
  4. Got a 404 error instead of a login page.

Expected Behavior

  • The Kick OAuth authorization page should open and prompt the user to log in.

Actual Behavior

  • Instead, I get a 404 error.

Additional Information

  • I followed the documentation here but it doesn't seem to be working.
  • I contacted Kick support, and they advised me to report it here.

Any updates or fixes would be appreciated!

Activity

  1. IAmTheHouse-X commented on Feb 20, 2025

    @IAmTheHouse-X
    Contributor

    Thanks for opening an issue!

    It looks like you are calling https://id.kick.com/oauth2/authorize

    Where you should be calling https://id.kick.com/oauth/authorize

    Just a typo in the endpoint. Let us know if it fixes your problem!

  2. caenvibe commented on Feb 20, 2025

    @caenvibe
    Author

    OAuth 2.0 Authorization Endpoint Still Returning 404

    Hi,

    Thanks for your response! I updated my authorization endpoint to https://id.kick.com/oauth/authorize as you suggested. However, I am still getting an HTTP 404 error when trying to access it.

    Here’s the exact request I’m making:

    https://id.kick.com/oauth/authorize?client_id=MY_CLIENT_ID&redirect_uri=http://localhost:5000/callback&response_type=code

    Could you confirm if this endpoint is active and correctly implemented? Or is there an updated URL that we should be using?

    Looking forward to your response. Thanks for your help!

    Best regards,
    [Caenvibe]

  3. IAmTheHouse-X commented on Feb 20, 2025

    @IAmTheHouse-X
    Contributor

    It looks like some of the required parameters are missing from the url.

    Image

    A valid url looks like below:

    https://id.kick.com/oauth/authorize?response_type=code&client_id=CLIENTID&state=MYSTATE&scope=MYSCOPES&redirect_uri=MYCALLBACK&code_challenge=MYCODECHALLENGE&code_challenge_method=S256

    Check out here for some code examples that have been made by the community.

    Also, jump into the Kick Discord #community-developers channel! Theres heaps of friendly developers that are tackling the same problems!

  4. caenvibe commented on Feb 20, 2025

    @caenvibe
    Author

    Hi, I am still getting a 500 Internal Server Error when trying to authorize via https://id.kick.com/oauth/authorize. My request URL is formatted correctly and contains all required parameters (client_id, redirect_uri, code_challenge, etc.), but the server is returning an error. Can you confirm if the OAuth server is functioning correctly? Thanks!

  5. caenvibe commented on Feb 20, 2025

    @caenvibe
    Author

    Hello,
    I was able to get to the allow access screen, but after allowing it, I get {"message":"Internal Server Error"} error. How can I solve this?

    This happens after the site link https://api.kick.com/oauth/authorize allows access.

    Please help me, good work.

  6. locked and limited conversation to collaborators on Feb 20, 2025
  7. converted this issue into a discussion #49 on Feb 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions