Kick Discovery Scraper

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, 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:

{ "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:

{
    "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 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.