Use case / Problem
I run a casino stream on Kick where viewers request specific slots to be played live, and we share the winnings. To avoid typos and disputes over slot names, I built a custom website where viewers pick a slot from a dropdown and submit their request.
I wanted to tie this to native Kick Channel Points so viewers spend points to place a request. However, the current API does not support this use case.
What is missing
- No endpoint to read a viewer's channel points balance
- No endpoint to add or subtract channel points for a specific user
- No way to attach custom metadata to a redemption (e.g. slot name from external system)
What we need
GET /channels/{channel}/points/users/{user} → read balance
POST /channels/{channel}/points/users/{user} → increment / decrement balance
PATCH /redemptions/{id} → attach metadata or mark as fulfilled
Why this matters
Without this, any interactive economy built on top of Kick Channel Points requires a completely parallel points system that is invisible to viewers in the native UI. This creates confusion and reduces engagement.
This would benefit: casino streamers, game show formats, prediction systems, loyalty programs, and any creator running interactive viewer economies.
Current workaround
External database + custom site + manual moderation. Not scalable and error-prone.
Use case / Problem
I run a casino stream on Kick where viewers request specific slots to be played live, and we share the winnings. To avoid typos and disputes over slot names, I built a custom website where viewers pick a slot from a dropdown and submit their request.
I wanted to tie this to native Kick Channel Points so viewers spend points to place a request. However, the current API does not support this use case.
What is missing
What we need
Why this matters
Without this, any interactive economy built on top of Kick Channel Points requires a completely parallel points system that is invisible to viewers in the native UI. This creates confusion and reduces engagement.
This would benefit: casino streamers, game show formats, prediction systems, loyalty programs, and any creator running interactive viewer economies.
Current workaround
External database + custom site + manual moderation. Not scalable and error-prone.