# Kick Playback Scraper (`romy/kick-playback-scraper`) Actor Get real, signed HLS playback URLs for live/DVR/VOD streams 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-playback-scraper.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 $1.20 / 1,000 playback 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 Playback Scraper do? **Kick Playback Scraper** takes one or more Kick livestream or VOD ids and pushes real, signed HLS (`.m3u8`) playback URLs for each — one dataset row per id. It talks directly to the same internal API the official [Kick](https://kick.com/) Android app uses (`mobile.kick.com`), reverse-engineered by capturing and analyzing live traffic from the real app. No Kick account, no API key. This is the playback-URL 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 Playback Scraper? - **Real, signed URLs that actually play** — not placeholder links, confirmed live against real live streams and VODs - **Handles Kick's undocumented request-body requirement** — the endpoint silently 400s on a bare POST; this Actor sends the exact trimmed telemetry body Kick's backend requires, discovered by capturing the real app's traffic - **No account needed** — every request works fully anonymously - **Use cases:** building a custom player, monitoring stream availability, archiving VOD manifests, downstream HLS processing pipelines ### Input | Field | Type | Description | | ----------- | -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `streamIds` | string\[] | **Required.** A Kick livestream id (from [kick-discovery-scraper](https://apify.com/romy/kick-discovery-scraper) or `GET /livestreams`) or a VOD id (from [kick-vod-scraper](https://apify.com/romy/kick-vod-scraper)). This is NOT a channel id or slug. | Example: ```json { "streamIds": ["124912670"] } ``` ### Output One dataset row per stream id: ```json { "streamId": "01a05572-6ef0-7270-8f8c-042989822a75", "playback": { "playback_url": { "dvr": "https://stream.kick.com/.../byte-range-multivariant.m3u8", "live": "https://....playback.live-video.net/api/video/v1/....m3u8?token=...", "thumbnail": "https://stream.kick.com/.../thumbnail-sheet-{index}.webp", "vod": "https://web.kick.com/api/v1/stream/manifest.m3u8?init=...", "vod_session": "https://web.kick.com/api/v1/stream/vod_session?init=..." }, "user_session": { "...": "echoed session/telemetry fields" }, "video_player": { "...": "echoed player fields" }, "video_session": { "video_id": "01a05572-6ef0-7270-8f8c-042989822a75", "video_stream_status": "live", "...": "more" } } } ``` ### Known limitations - A stream/VOD id that has ended, been deleted, or never existed will legitimately fail (400/404) — this Actor logs and skips it rather than aborting the whole run. - No login flow — read-only, guest-accessible data only, by design (see the parent Actor's Known limitations). - 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 pricing. You're charged a `playback` event ($0.002 on the FREE plan) for each stream id whose playback info is successfully fetched. See the Actor's Pricing tab for current rates. # Actor input Schema ## `streamIds` (type: `array`): A Kick livestream id (from kick-discovery-scraper's livestreams/home resource, or GET /livestreams) or a VOD id (from kick-vod-scraper). This is NOT a channel id or slug. ## Actor input object example ```json { "streamIds": [ "01a05572-6ef0-7270-8f8c-042989822a75" ] } ``` # 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 = { "streamIds": [ "01a05572-6ef0-7270-8f8c-042989822a75" ] }; // Run the Actor and wait for it to finish const run = await client.actor("romy/kick-playback-scraper").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 = { "streamIds": ["01a05572-6ef0-7270-8f8c-042989822a75"] } # Run the Actor and wait for it to finish run = client.actor("romy/kick-playback-scraper").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 '{ "streamIds": [ "01a05572-6ef0-7270-8f8c-042989822a75" ] }' | apify call romy/kick-playback-scraper --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,romy/kick-playback-scraper" } } } ``` 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/iOUyNq6Tl7bqAdhJ6/builds/qfO76dIu97mG2qA11/openapi.json