Kick · Posts and media

Kick Clip Scraper API

The Kick Clip endpoint is one API call: send a URL with your HProxy key and get back a clean, structured JSON object. Pull a single Kick clip from its URL: title, the clipper, the channel, duration, view count and a direct media URL. HProxy runs the proxies, sessions, anti-bot handling and parsing server-side, so there is no headless browser to babysit and no parser to keep fixing when Kick changes its markup. You only ever touch the JSON.
  • 0.15¢ per call
  • $1.49 per 1,000
  • Takes a URL
  • Errors and timeouts are not charged

The call

One GET, and the clip comes back as JSON.

Your key goes in one header. 1 required parameter, and the answer is the object below it.

The full reference
curl "https://hproxy.com/api/v1/scrape/kick/clip?url=https%3A%2F%2Fkick.com%2Ftrainwreckstv" \
  -H "X-API-Key: hpx_your_key_here"
Response200 OK · JSON
{
  "id": "72901...",
  "caption": "how we shipped it in a weekend",
  "author": { "username": "@handle", "followerCount": 90421 },
  "stats": { "views": 421903, "likes": 38210, "comments": 1204, "shares": 903 },
  "media": { "url": "https://.../video.mp4", "duration": 47.2 }
}

What comes back

The Kick clip object.

caption / title
The media's caption or title text.
stats
Views, likes, comments and shares.
author
Uploader handle, ID and follower count.
media
Direct media URLs, duration and dimensions.

What it takes

Parameters.

urlurlRequiredhttps://kick.com/trainwreckstv

Target URL (profile, post or video).

trimbooleantrue

Return a slimmed-down payload (drops verbose fields).

How it works

Scraping Kick clip, in three steps.

You write one line. Proxies, anti-bot walls, rendering and parsing happen on our side.

  1. 1

    Create a free account

    Sign up and top up any amount. The balance pays for every HProxy product.
  2. 2

    Grab your API key

    One key from the dashboard authenticates every scraper.
  3. 3

    Call the endpoint

    Send the GET you need and read the JSON. That is the entire integration.

What people build with it

Where the Kick clip endpoint earns its keep.

  • Track how Kick videos perform over time.
  • Build a media library with captions, stats and download URLs.
  • Benchmark competitor content and hooks.

Kick clip questions

Answered before you ask.

The reference

Send one authenticated HTTPS request to the Kick Clip endpoint with a URL and your HProxy API key. Pull a single Kick clip from its URL: title, the clipper, the channel, duration, view count and a direct media URL. No proxies, no headless browser and no parsing on your side. The response is ready-to-use JSON.

This endpoint is 0.15¢ per successful call, which is $1.49 per 1,000. It bills from your HProxy balance with no subscription and no monthly minimum. Errors are retried and never charged; a lookup whose target does not exist counts as a call.

The API only accesses publicly available Kick data, the same pages anyone can open in a browser. You are responsible for using the data in line with applicable laws and Kick's terms for your use case.

A structured JSON object with the full clip data Kick exposes publicly. See the fields listed above. The schema is consistent across calls, so you integrate once and rely on it.

No. Every call runs on HProxy's own residential network behind the scenes, so requests look like real users. The proxy layer is already included in the per-call price.

More on the Kick Clip API

What the Kick Clip endpoint returns

Pull a single Kick clip from its URL: title, the clipper, the channel, duration, view count and a direct media URL. The JSON object carries caption / title, stats, author and media. Nothing is summarised away on our side, so what you read in the response is what the Kick clip page itself holds.

What you send to the Kick Clip API

The call takes a URL. Required: url. Optional: trim. Your key travels in the X-API-Key header, the response is JSON, and the call is billed at 0.15¢, $1.49 per 1,000.

Posts and media on other platforms

The same posts and media data is available on 13 other platforms: Twitch Clip, TikTok Video, Facebook Profile Reels, YouTube Channel Videos, Instagram User Reels, LinkedIn Company Posts, Twitter / X User Tweets, Reddit Subreddit Posts, Threads User Posts, Pinterest Pin, Bluesky User Posts, Spotify Track and Truth Social User Posts. They share this endpoint's JSON shape, its per-call billing and your one API key, so moving from Kick to another network is a change of URL rather than a second integration.

Is scraping Kick clip allowed?

The endpoint reads publicly available Kick data, the same pages anyone can open in a browser without logging in. It does not touch private accounts or anything behind a password. How you then use the data is yours to keep lawful, under the rules that apply to you and to Kick.

Ready when you are.

Your dashboard is ten seconds away. No sales call, no subscription, no minimum.