Skip to content

Question: Using /api/v2 endpoints in production #348

@firas357952

Description

@firas357952

Hello Kick Dev Team,

I’m currently developing a production-level integration using the official Kick API documented at https://docs.kick.com.

At the moment I’m using the documented v1 endpoints, which work well, but they lack some information that my application requires.

While inspecting the network requests used by the Kick website, I noticed some v2 endpoints that return the additional data I need. For example:

https://kick.com/api/v2/channels/{username}

This endpoint appears to provide more detailed channel information and works reliably in testing, but it is not currently listed in the official API documentation.

Before relying on endpoints like this in production, I wanted to ask:

• Are the /api/v2 endpoints intended for third-party developer use?
• Are these endpoints considered internal and subject to change?
• Is there a plan to officially publish these endpoints in the documented API in the future?

Since this project is intended for production use, I want to ensure it follows Kick’s recommended practices and avoids relying on unsupported or unstable APIs.

Thank you for your time and clarification!

Best regards.

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