Kick API
GET /public/v1/categories/{id} endpoint removal
Deprecated, no dateSubscribe to Kick APIShare
Kick API deprecated GET /public/v1/categories/{id} without a shutdown date. The endpoint will be removed in due time, and calls will fail once it is taken down.
Calls it hits
GET /public/v1/categories/{id}
What to use instead of these calls
Use GET /public/v2/categories?id={category_id} instead.
In Kick API's words
As a result, the V1 endpoints for Categories are now deprecated and will be removed in due time.
Facts
- API
- Kick API
api.kick.com - Kind
- Endpoint removal
- Announced
- January 15, 2026
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Kick API's own pages
Questions
When does this change take effect?
Kick API deprecated GET /public/v1/categories/{id} without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Kick API has not given a shutdown date yet.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
More from Kick API 3
-
No date
GET /public/v1/categoriesEndpoint removal Deprecated, no date -
No date
GET /public/v1/livestreamsEndpoint removal Deprecated, no date -
No date
POST /public/v1/token/introspectEndpoint removal Deprecated, no date
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.