Skip to content

Expose channel-user trust fields for anti-bot giveaway dashboards #389

@losttrader174-oss

Description

@losttrader174-oss

Hi Kick Developer Team,

My name is Abhijeet. I am building an experimental anti-bot giveaway dashboard for Kick streamers. The use case is large chat-based giveaways where viewers post wallet addresses directly in Kick chat.

The dashboard already uses Kick OAuth and webhooks to receive events such as chat.message.sent, channel.followed, channel.subscription.new, channel.subscription.renewal, channel.subscription.gifts, and kicks.gifted.

The goal is to help streamers:

  • detect wallet addresses in chat
  • extract attached messages
  • deduplicate users and wallets
  • flag suspicious bot-like entries
  • show message history for selected entrants
  • prevent duplicate winner selection
  • keep the giveaway fully inside Kick chat without external forms

Request

Could Kick expose official backend-safe access to the same trust fields that appear in the Kick chat profile card?

Requested fields:

user_id
username
slug
profile_picture
created_at / joined_on
following_since for the current channel
subscribed_for
current_subscriber_status
subscription_started_at
subscription_expires_at
gifted_sub_count in the channel
KICKs gifted in the channel
badges
is_moderator
is_banned / banned status
Ideal Options
Either include these fields in the chat.message.sent sender payload:

sender.created_at
sender.following_since
sender.subscribed_for
sender.badges
sender.is_subscriber
sender.is_moderator
sender.is_banned
Or expose an official endpoint such as:

GET /public/v1/channels/{channel_id}/users/{user_id}
or:

GET /public/v1/channels/{channel_slug}/users/{username}
This would allow approved dashboard apps to retrieve account age, follow age, sub status, badges, and channel-specific safety context without relying on unsupported frontend/internal endpoints.

High-Volume Use Case
This dashboard is intended for large streamer giveaways, potentially 40,000+ viewers and thousands of chat messages per minute.

Could the team clarify:

webhook delivery limits for chat.message.sent
event subscription limits
rate limits for channel-user lookup endpoints
whether apps can be verified or allowlisted for high-volume channels
webhook retry behavior and delivery guarantees
whether per-user watchtime is available to approved broadcaster apps
Why This Matters
For giveaway anti-bot filtering, the most important trust signals are:

account age
follow age
watch hours
sub status
gift history
message history
duplicate wallet usage
bot-like spam behavior
The current public webhooks are enough for real-time chat and wallet detection, but account age and historical follow age are not currently available through the documented public API.

Official access to these fields would make it possible to build safer, fairer, and more transparent giveaway tooling for Kick streamers.

Thank you.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions