# Kick Live Chat Stream Scraper (`romy/kick-live-chat-stream`) Actor Get near-real-time chat messages — no other Kick scraper on the Store offers live chat capture from Kick. Talks directly to Kick's own mobile app API, no login needed. Split from the mature, published kick-all-in-one-api for a focused, single-purpose workflow. - **URL**: https://apify.com/romy/kick-live-chat-stream.md - **Developed by:** [Romy](https://apify.com/romy) (community) - **Categories:** Other - **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing from $9.40 / 1,000 chat message chargeds This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events. Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have. Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event ## What's an Apify Actor? An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes. In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours, and optionally produces a well-defined JSON output, datasets with results, or files in key-value store. In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server. Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md. ## How to integrate an Actor? If asked about integration, you help developers integrate Actors into their projects. You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready. Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run. For examples already wired to this Actor's own input schema, see the [API](#api) section below. Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`). # README ### What does Kick Live Chat Stream do? **Kick Live Chat Stream** captures a [Kick](https://kick.com/) channel's live chat for a bounded time window — give it a channel id and a duration, get back every chat message posted during that window, one dataset row per message. It talks directly to the same internal API the official Kick Android app uses (`mobile.kick.com`'s chat history endpoint), reverse-engineered by capturing and analyzing live traffic from the real app. No Kick account, no API key needed to read. This is the chat-capture slice of [Kick All-in-One API](https://apify.com/romy/kick-all-in-one-api), split out as its own focused Actor. ### Why use Kick Live Chat Stream? - **The only Kick chat-capture Actor on Apify Store** — no other Kick scraper offers chat capture at all, live or bounded - **No WebSocket client needed on your end** — this Actor polls Kick's own REST-pollable chat history endpoint internally and hands you back plain dataset rows - **Deduplicated automatically** — the same poll-and-diff technique the parent Actor's SSE stream uses internally, so you never get the same message twice across polls - **No account needed** — works fully anonymously - **Use cases:** chat sentiment/moderation snapshots, spike-driven chat capture around a moment in a stream, lightweight chat archiving without holding a connection open indefinitely ### How it connects to the parent The parent Actor, [kick-all-in-one-api](https://apify.com/romy/kick-all-in-one-api), exposes `GET /channels/{id}/chat/stream` as an always-on Server-Sent Events connection (via Apify Standby) — built on top of Kick's plain REST-pollable `GET /channels/{id}/chat/history` endpoint, which it polls on an interval and forwards new, de-duplicated message batches over SSE. This Actor reuses that exact poll-and-diff technique (same interval-based polling, same seen-message-id de-duplication with bounded eviction), but adapts it to how ordinary Apify Actors run: a single batch job with a bounded lifetime, not an always-open Standby connection. Instead of streaming SSE events to an open HTTP connection, it polls internally for `durationSeconds` and pushes each new message straight to the Actor's dataset, then exits. ### Input | Field | Type | Description | | ----------------- | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | `channelId` | string | Optional. Numeric Kick channel id (NOT the slug); leave empty to follow the busiest channel that is live right now — from [kick-channel-profile-scraper](https://apify.com/romy/kick-channel-profile-scraper) or `GET /channels/{slug}` on the parent Actor. | | `durationSeconds` | integer | How long to poll for new messages before stopping. Default `60`, capped at `300` (5 minutes). | | `intervalMs` | integer | How often to poll internally. Default `3000`, floor of `1000`. | | `startTime` | string | ISO 8601. Only capture messages posted after this time. Defaults to the run's start time. | Example: ```json { "channelId": "18750821", "durationSeconds": 120, "intervalMs": 3000 } ``` ### Output One dataset row per captured chat message, in the shape Kick's own app receives: ```json { "id": "c62e3b2d-...", "chat_id": 4351775, "user_id": 12345678, "content": "gg", "type": "message", "sender": { "username": "3sam55", "identity": { "badges": [{ "type": "subscriber" }] } }, "created_at": "2026-08-31T10:15:30Z" } ``` If no chat activity occurs during the capture window, the run completes cleanly with zero dataset rows — this is expected on a quiet or offline channel, not an error. ### Known limitations - **This is a bounded, one-shot capture, not a live/continuous stream.** It polls for exactly `durationSeconds` and then stops — messages posted after the run ends are not captured. If you need a truly always-open connection, use the parent Actor's `GET /channels/{id}/chat/stream` (Standby SSE) directly. - **Latency is bounded by `intervalMs`** (default 3000ms) — same tradeoff as the parent's SSE bridge, since both are REST-polling underneath, not Kick's own WebSocket push channel. - Despite the bounded-window tradeoff, this is still the only chat-capture capability among Kick scrapers on Apify Store — every other listing wraps stream/channel/clip metadata, none capture chat. - This is an unofficial, reverse-engineered integration, not affiliated with or endorsed by Kick Streaming, Inc. Behavior may change if Kick changes its API. ### Pricing Pay-per-event, billed per `chat-message` event — one charge per chat message captured during the run. FREE tier: $0.01/message. This is the only Kick actor on the Apify Store offering live/bounded chat capture, priced to reflect that unique capability. See the Actor's Pricing tab for current tier rates. # Actor input Schema ## `channelId` (type: `string`): Numeric Kick channel id (NOT the channel slug). Get it from kick-channel-profile-scraper or GET /channels/{slug} on the parent Actor. Optional: leave empty and the busiest channel that is live right now is followed -- a fixed channel goes offline. ## `durationSeconds` (type: `integer`): How long to poll for new chat messages before stopping. Default 60, capped at 300 (5 minutes) since this is a bounded batch run, not an always-open stream. ## `intervalMs` (type: `integer`): How often to poll Kick's chat history endpoint internally. Default 3000ms, floor of 1000ms. ## `startTime` (type: `string`): Only capture messages posted after this time. Defaults to the current time (i.e. only new messages during the run). ## Actor input object example ```json { "durationSeconds": 60, "intervalMs": 3000 } ``` # Actor output Schema ## `dataset` (type: `string`): No description # API You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup. ## JavaScript example ```javascript import { ApifyClient } from 'apify-client'; // Initialize the ApifyClient with your Apify API token // Replace the '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = {}; // Run the Actor and wait for it to finish const run = await client.actor("romy/kick-live-chat-stream").call(input); // Fetch and print Actor results from the run's dataset (if any) console.log('Results from dataset'); console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`); const { items } = await client.dataset(run.defaultDatasetId).listItems(); items.forEach((item) => { console.dir(item); }); // 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs ``` ## Python example ```python from apify_client import ApifyClient # Initialize the ApifyClient with your Apify API token # Replace '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = {} # Run the Actor and wait for it to finish run = client.actor("romy/kick-live-chat-stream").call(run_input=run_input) # Fetch and print Actor results from the run's dataset (if there are any) print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}") for item in client.dataset(run.default_dataset_id).iterate_items(): print(item) # 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start ``` ## CLI example ```bash echo '{}' | apify call romy/kick-live-chat-stream --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,romy/kick-live-chat-stream" } } } ``` The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer ` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations). ## OpenAPI specification Download the OpenAPI definition: https://api.apify.com/v2/actors/ChXAgBthttMZrO8D0/builds/f4Wfb2r7NkOwzlHGC/openapi.json