Clip
1 credit/v1/kick/clipGet Kick clip details.
url
Kick APIFetch Kick clip data with one API
Fetch public Kick data as structured JSON with one SocialCrawl API key. Same Post, Comment, and Author schema as every other platform. Reads are priced in credits.
/v1/kick
1 active endpoint
- GET /v1/kick/clip
What Kick endpoints does SocialCrawl ship?
1 live read endpoint for public Kick clip data. Data API only.
Kick API1 endpoint supported
View docsReturns one Kick clip: title, view count, duration, category, creator name, channel name, thumbnail URL, and when it was created.
Use it when you have a Kick clip URL, and note it is the only Kick endpoint, so channels and live streams are not covered.
1 credit
GET/v1/kick/clip?url=https%3A%2F%2Fkick.com%2Fxqc%2Fclips%2Fclip_abc123
url · Full URL of the Kick clip
$ curl https://www.socialcrawl.dev/v1/kick/clip?url=https%3A%2F%2Fkick.com%2Fxqc%2Fclips%2Fclip_abc123 \
-H "x-api-key: sc_YOUR_API_KEY"idle
// Running this live needs your own API key. Hit "Try it" to see an example responseHow the Kick API works
Kick is a normal SocialCrawl social surface. You call GET /v1/kick/… with an API key, spend credits on live misses, and get a single JSON envelope back. No second SDK.
Authenticate every call
Send your key in the x-api-key header. The same key works across the SocialCrawl catalog.
GET with query params
Routes are GET. Pass handles, urls, queries, and cursors as query strings. We validate formats before charging.
Pay in credits, not seats
Live misses debit the route tier. Cache hits cost 0. Empty or hard failures refund.
Read one JSON envelope
Every response is the same shape: success, data, credits_used, credits_remaining, request_id, cached.
The usual integration chain
Most callers resolve a public Kick clip URL to structured JSON.
01URL
GET /v1/kick/clipPublic Kick clip URL
Pass the clip link as the query param.
02Clip
GET /v1/kick/clipStructured clip record
One standard credit read on live miss.
03Cache
GET /v1/kick/clipcredits_used 0 on hit
Recurring lookups stay cheap.
04Pipeline
GET /v1/kick/clipShared envelope for downstream jobs
Same auth and billing as the rest of SocialCrawl.
request
GET /v1/kick/clip
?url=https://kick.com/xqc/clips/clip_abc123
Host: www.socialcrawl.dev
x-api-key: sc_your_api_key_hereresponse envelope
{
"success": true,
"data": { "/* Author | Post | PostList | CommentList | … */": true },
"credits_used": 1,
"credits_remaining": 9999,
"request_id": "req_…",
"cached": false
}What lands in data
Field names match the rest of SocialCrawl where archetypes align.
Authorclip
id, username, display_name, avatar_url, bio, followers, url, ext
PostList / Postclip
items[].post with id, url, content, engagement, author, published_at, ext
CommentListclip
items[] with author, content.text, engagement, published_at when comments ship
Search / Mediaclip
search hits, media metadata, or transcripts depending on route
Inside the gateway
Same request lifecycle as every other /v1 platform endpoint.
- 01
Edge receives the call
Next.js catch-all routes into the Hono social API. We mint a request_id, authenticate the key, then enforce rate limit and concurrency.
- 02
Validate, then debit
Registry lookup finds the route. Required params run first. Invalid input returns 400 with no charge. Valid calls debit before upstream work.
- 03
Cache or fetch
A deterministic cache key is built from platform + resource + params. Hit: credits_used = 0. Miss: upstream fetch with retries and circuit breaker.
- 04
Normalize and return
Upstream JSON is mapped to Author / Post / PostList / CommentList (or route archetype), validated, wrapped in the success envelope, and logged for billing audit.
Billing rules that matter in production
- Standard live miss: tier cost (often 1 credit)
- Advanced reads: typically 5 credits
- Premium reads: typically 10 credits
- Metered routes: min floor when documented
- Cache hit: 0 credits
- Empty / hard fail: auto-refund
- Bad params: 400, never charged
- No credits: 402, never charged
- Disabled routes: 503, never charged
How we get the data
Kick is public-read data on SocialCrawl. We normalize it into the shared schema so your code does not learn a second OAuth flow.
What Kick is for this API
Public Kick surfaces exposed by the registry. Read-only for research, monitoring, and product jobs.
How SocialCrawl reaches it
Social-read upstreams behind one gateway. Prism composites combine legs when a fat route is registered.
What leaves our edge
Unified JSON envelope: success, data, credits_used, request_id, cached. Shared Author / Post / Comment leaves where archetypes align.
What we do not ship live
No write endpoints and no private inbox. Disabled routes stay out of the active count. Prefer registry docs for the live inventory.
field map sketch
upstream identity→ author.* / data rootprofile identity and counters
public post / media→ post.* / items[].postpost content and engagement
list / search page→ items[] or hitscomments or search hits when present
What this API is used for
The jobs this API is most often used for.
1active Kick endpoints in the registry
1credits per live clip miss
Kick monitoring and content intelligence
Callers concentrate on profile, content lists, search, and deepen paths on Kick. Structured Kick JSON on the shared schema with one SocialCrawl API key.
Detail reads are typically a few seconds on live miss. Search and fat composites are slower paths.
Use case examples
Common ways teams put this data to work, and the stack each one tends to run.
Monitoring jobs
Python, cron, Slack botsPoll profiles and feeds on Kick. Alert when engagement velocity jumps.
Research and VoC
Node, notebooks, BI loadsSearch and expand posts for brand, product, and competitor language on Kick.
Backend product jobs
Go, workers, ExplorerWire resolve to list to detail into pipelines. Cache hits keep recurring runs cheap.
Call it in two lines
Live misses spend credits by tier. Cache hits are free. Empty or hard failures refund.
curl "https://www.socialcrawl.dev/v1/kick/clip?url=https://kick.com/xqc/clips/clip_abc123" \
-H "x-api-key: sc_your_api_key_here"curl "https://www.socialcrawl.dev/v1/kick/clip?url=https://kick.com/xqc/clips/clip_abc123" \
-H "x-api-key: sc_your_api_key_here"Same key as the rest of the catalog
Endpoints
What data does the Kick API return?
Every endpoint returns structured JSON in a unified envelope. Computed fields such as engagement rate and content category are included only where the endpoint supports them and the required source inputs are present.
Comparison
How does SocialCrawl compare to DIY scraping for Kick data?
Same Kick data, two very different paths. Auth, rate limits, schema, and cost, side by side.
| Feature | SocialCrawl | DIY scraping |
|---|---|---|
| Setup | Sign up and send one GET request | Headless browser, proxies, and parser code to build first |
| Authentication | One x-api-key header | None, but you handle blocks and bot detection yourself |
| Response schema | Unified JSON shared across 51 platforms | Raw HTML you parse and normalize yourself |
| Pricing | 1 credit per request; 100 free credits on signup | Proxy and server costs plus engineering hours |
| Maintenance | SocialCrawl absorbs Kick markup changes upstream | Your scraper breaks whenever Kick changes its frontend |
Setup
SocialCrawl
Sign up and send one GET request
DIY scraping
Headless browser, proxies, and parser code to build first
Authentication
SocialCrawl
One x-api-key header
DIY scraping
None, but you handle blocks and bot detection yourself
Response schema
SocialCrawl
Unified JSON shared across 51 platforms
DIY scraping
Raw HTML you parse and normalize yourself
Pricing
SocialCrawl
1 credit per request; 100 free credits on signup
DIY scraping
Proxy and server costs plus engineering hours
Maintenance
SocialCrawl
SocialCrawl absorbs Kick markup changes upstream
DIY scraping
Your scraper breaks whenever Kick changes its frontend
FAQ
Have a question? We got answers
Find answers to frequently asked questions about SocialCrawl's API, pricing, and capabilities.
Contact usHow do I scrape Kick.com data with an API?
SocialCrawl exposes a Kick Clip endpoint that returns normalized clip data by URL. Send a GET request with x-api-key. No Kick developer app, no OAuth 2.1 client approval, no refresh-token flow required.
Is there a Kick data API?
Yes. SocialCrawl is a Kick data API focused on public clip data: one GET on a clip URL returns title, view count, duration, category, creator, channel, and thumbnail as unified JSON. Kick's own public API launched in 2024 and is the right tool for managing your channel, but it requires OAuth 2.1, a registered application, and client approval. For reading public clip data, SocialCrawl needs only one x-api-key, at 1 credit per request with 100 free credits to start.
What Kick endpoints does SocialCrawl offer today?
One endpoint covers the highest-demand use case: clip details (title, view count, duration, category, creator name, channel name, thumbnail URL, created_at). Same unified schema as every other SocialCrawl platform.
Is this a Kick official API alternative?
Yes. Kick's public API launched in 2024 but requires OAuth 2.1, a registered application, and client approval. SocialCrawl reads public Kick clip data with one x-api-key, and responses match the schema shared across the other 50 platforms we support.
How much does the Kick API cost?
The Kick Clip endpoint costs 1 credit per request on the standard tier. New accounts get 100 free credits with no credit card required, enough to make 100 Kick clip calls before you pay a cent and validate the response end-to-end.
Is scraping Kick clips legal?
SocialCrawl reads only publicly visible Kick clip data through our upstream provider. You are responsible for complying with Kick's Community Guidelines, Terms of Service, and any data protection regulations that apply to your specific use case. SocialCrawl operates under a documented GDPR legitimate-interest framework: public, logged-out data only, no credential use, short-lived caches (2 to 30 minutes) with no persistent store, and a public opt-out channel for anyone whose public info appears in responses. Full details: socialcrawl.dev/legal/public-data-notice.
Can I use the Kick API for clip analytics and highlight reels?
Yes. The clip endpoint returns view count, duration, category, and thumbnail URL, ideal for ranking clips by engagement, building streamer highlight feeds, feeding moderation pipelines, or enriching social analytics dashboards with Kick alongside Twitch and YouTube.
What is the best Kick scraper API?
SocialCrawl offers a focused Kick clip endpoint that returns title, view count, duration, category, creator, channel, and thumbnail for 1 credit per request. 100 free credits on signup, no card. Compared with DIY scraping, you skip proxies, parsers, and breakage, and the response uses the same unified schema as 50 other platforms.
Ask AI about SocialCrawl