Skip to content

Is API-driven, streamer-consented sponsored chat messaging permitted? (marketing-activities authorization) #392

@janebautina

Description

@janebautina

Hi Kick team,

We're a registered Kick developer app (Client ID 01KM62J8KCJHFYBGZ055XWXED6, bot Alesha) building a live-chat assistant. We emailed [email protected] and were pointed here for a developer answer.

Per the Kick Developer Terms of Service, API use for "marketing activities … services used by marketers, promoters, or their customers for marketing campaigns" is permitted "only after entering into a separate agreement and running through an approval process."

Our use case: a streamer opts in and approves a campaign; our dedicated bot then posts a small number of clearly labeled sponsored messages (#Ad / "Sponsor: …") into that streamer's chat via the official API, with the streamer's Branded Content disclosure enabled. Streamers consent per-campaign; we do no behavioral targeting and never transfer chat/user data to ad networks.

Questions:

  1. Is there currently a process to obtain the "separate agreement / approval" the Developer ToS references for marketing use of the API? If so, how do we start it?
  2. If that process isn't yet implemented, is streamer-consented, clearly-labeled sponsored chat messaging permitted under the standard developer agreement in the interim, or should we hold until the process exists?
  3. Any constraints we should design around (send-message rate limits, required disclosure mechanics, eligible creator tiers)?

Thanks — we'd rather build this within your rules than around them.

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