# Kick Discovery Scraper (`romy/kick-discovery-scraper`) Actor

Browse Kick's home feed, livestreams, categories, and search — one dataset row per result. Talks directly to Kick's internal mobile app API, so no account or API key is needed. Derived from romy/kick-all-in-one-api, split out as a focused batch-run discovery Actor.

- **URL**: https://apify.com/romy/kick-discovery-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 $3.12 / 1,000 result pusheds

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 Discovery Scraper do?

**Kick Discovery Scraper** pulls Kick's browse/discovery surfaces — the home feed of featured live channels, the full browsable & filterable livestreams listing, every game/category, and full-text search — one dataset row per result item.

It talks directly to the same internal APIs the official Kick Android app uses (`kick.com`, `mobile.kick.com`, `search.kick.com`), reverse-engineered by capturing and analyzing live traffic from the real app. No Kick account, no API key. This is the discovery slice of [Kick All-in-One API](https://apify.com/romy/kick-all-in-one-api), split out as its own focused batch-run Actor.

### Why use Kick Discovery Scraper?

- **Real, confirmed-live filters and pagination** — `language` and `category_id` genuinely filter `/livestreams` (confirmed by testing values directly against the API); `/home`, `/livestreams`, and `/categories` all paginate for real, with distinct pages returning non-overlapping items
- **Four discovery surfaces, one Actor** — home feed, livestreams, categories, and search all in one `resource` switch
- **No account needed** — every endpoint works fully anonymously
- **Use cases:** stream discovery bots, category/niche tracking, building a channel-id seed list for downstream Actors (profile, VOD, clips, chat scrapers), trending-content monitoring

### Input

| Field        | Type    | Description                                                                                      |
| ------------ | ------- | ------------------------------------------------------------------------------------------------ |
| `resource`   | string  | **Required.** One of `home`, `livestreams`, `categories`, `search`. Default `livestreams`.       |
| `query`      | string  | Required when `resource` is `search`. Free-text query across channels, categories, livestreams.  |
| `sort`       | string  | `livestreams` only: `viewer_count_desc` (default) or `featured`.                                 |
| `language`   | string  | `livestreams` only: ISO 639-1 code, e.g. `en`. Confirmed live to genuinely filter results.       |
| `categoryId` | integer | `livestreams` only: from `resource=categories`.                                                  |
| `limit`      | integer | Page size. Default 24 for livestreams, 32 for categories.                                        |
| `maxPages`   | integer | Stop after this many pages. Default `5`. Ignored for `search` (always a single call).            |
| `maxItems`   | integer | Stop once at least this many items have been pushed. Default: unlimited (bounded by `maxPages`). |

Example:

```json
{ "resource": "livestreams", "language": "en", "sort": "viewer_count_desc", "maxPages": 3 }
```

### Output

One dataset row per item. Shape depends on `resource` — a real trimmed `livestreams` row:

```json
{
    "id": "01a05572-6ef0-7270-8f8c-042989822a75",
    "title": "YOLO VOLVIÓ POR KAREN !! 😱😱",
    "viewer_count": 40160,
    "channel": { "id": 56488514, "slug": "yoloaventuras", "username": "YoloAventuras" },
    "category": { "id": 8549, "name": "IRL", "slug": "irl" },
    "language": "es"
}
```

`search` rows are tagged with a `type` field (`livestream` | `channel` | `category`) since one call returns all three kinds mixed together.

### Known limitations

- `search` is capped by Kick's own backend at ~3 results per category (channels/categories/livestreams), confirmed live with no pagination possible — treat it as quick suggestions, not an exhaustive search; use `livestreams` or `categories` for a full listing.
- `livestreams`' `sort` is a strictly-validated required enum on Kick's backend — this Actor always sends a valid value, so you never need to worry about a `400`.
- Channel profile, VOD, clip, chat, and playback data are separate spin-off Actors from the same parent (see [kick-all-in-one-api](https://apify.com/romy/kick-all-in-one-api) for the full family).

### Pricing

Pay-per-event, `result` — charged once per item pushed to the dataset (livestream, channel, category, or search hit). Starts at $0.004 per result on the FREE plan; see the Actor's Pricing tab for tiered rates.

# Actor input Schema

## `resource` (type: `string`):

Which discovery endpoint to pull from.

## `query` (type: `string`):

Required when resource is "search". Free-text query across channels, categories, and livestreams.

## `sort` (type: `string`):

Sort order for results.

## `language` (type: `string`):

ISO 639-1 code, e.g. "en". Confirmed live to genuinely filter results.

## `categoryId` (type: `integer`):

From resource="categories".

## `limit` (type: `integer`):

Items per page. Default 24 for livestreams, 32 for categories.

## `maxPages` (type: `integer`):

Stop after this many pages (ignored for search, which is always a single call).

## `maxItems` (type: `integer`):

Stop once at least this many items have been pushed. Default: unlimited (bounded by maxPages).

## Actor input object example

```json
{
  "resource": "livestreams",
  "sort": "viewer_count_desc",
  "maxPages": 5
}
```

# 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 '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("romy/kick-discovery-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 '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("romy/kick-discovery-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 '{}' |
apify call romy/kick-discovery-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,romy/kick-discovery-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 <APIFY_API_TOKEN>` 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/TOLWwx9BXOb0p3IZV/builds/MPaFWbtr11KmtK6Jx/openapi.json