Kick data API
Read clips from Kick with one key and one response shape.
Kick is a live-streaming platform. Clips are the part of it that travels: a moment cut out of a stream, shared to X or TikTok, and often the first place a streamer's audience meets them. One endpoint reads a clip from its URL.
Clips are the whole surface here. There is no channel endpoint, no live-stream state, no VOD list, and no chat on this platform. If you need a streamer's channel or schedule, Twitch covers that shape and Kick does not.
Your first call
1. Fetch a clip
curl "https://www.socialcrawl.dev/v1/kick/clip?url=https://kick.com/xqc/clips/clip_01JGJHB6CEVFCQRYTVPM8DW892" \
-H "x-api-key: sc_your_key_here"const url = new URL("https://www.socialcrawl.dev/v1/kick/clip");
url.searchParams.set(
"url",
"https://kick.com/xqc/clips/clip_01JGJHB6CEVFCQRYTVPM8DW892",
);
const res = await fetch(url, { headers: { "x-api-key": process.env.SOCIALCRAWL_API_KEY! } });
const { data } = await res.json();
console.log(data.post.content.text, data.post.engagement.views);import os
import requests
res = requests.get(
"https://www.socialcrawl.dev/v1/kick/clip",
params={"url": "https://kick.com/xqc/clips/clip_01JGJHB6CEVFCQRYTVPM8DW892"},
headers={"x-api-key": os.environ["SOCIALCRAWL_API_KEY"]},
)
post = res.json()["data"]["post"]
print(post["content"]["text"], post["engagement"]["views"])Measured on 22/11/2026: this call returned one public clip from the xQc channel, with its title, view count and duration, for 1 credit.
2. Read what came back
The clip's title is in post.content.text, its view count in post.engagement.views, and its length in post.content.duration_seconds. The streamer is in post.author. post.content.media_urls is the playlist for the clip's video and thumbnail_url is its cover. post.published_at is when the clip was created.
3. Read computed fields
When an endpoint supports a computed field and the required source inputs are present, the unified response includes that optional field. Depending on the endpoint, optional fields can include engagement_rate, language, content_category, and estimated_reach. See Computed fields for formulas, clamping rules, and null semantics. Where an endpoint supports them, list rows also carry judged labels (computed.labels, computed.relevance) by default at no extra credits; see Labels.
What it covers
| What you want | Call |
|---|---|
| A clip's title, views and duration | GET /v1/kick/clip |
| Who made the clip and on which channel | GET /v1/kick/clip |
| The clip's video playlist and cover | GET /v1/kick/clip |
What it does not cover
- There is no channel data: no profile, follower count or schedule endpoint for a streamer.
- Live state, VOD lists and chat are not returned.
- Search. Start from a clip URL you already have.
- Clip comments are not returned.
Clips
The typical use is attribution. A Kick clip circulating on another platform carries only its URL. This endpoint turns that URL into the channel, the creator, and the view count, which is what you need to credit it or to size it against clips from Twitch or YouTube.
All endpoints
1 endpoint available.
| Endpoint | Path | Credit Tier |
|---|---|---|
| Get Kick clip details | /v1/kick/clip | standard (1cr) |
Platform notes
Views on a clip are cumulative and keep moving. A clip fetched a week apart legitimately reports two different numbers. There is no snapshot semantics here.
The URL must be a clip URL in the form kick.com/{channel}/clips/{clip_id}, not a channel or VOD URL.
Nothing on this platform paginates.
