# Kick (/docs/kick)



Kick [#kick]

Kick is a live-streaming platform, and 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.
`/v1/kick/clip` reads one of those clips from its URL for 1 credit.

Base URL: `/v1/kick/...`

Getting started [#getting-started]

One endpoint, one parameter. Pass the full clip URL.

```bash
curl "https://www.socialcrawl.dev/v1/kick/clip?url=https://kick.com/xqc/clips/clip_abc123" \
  -H "x-api-key: $SOCIALCRAWL_API_KEY"
```

What comes back [#what-comes-back]

`GET /v1/kick/clip` returns the clip's title, view count, duration, category, creator name,
channel name, thumbnail URL and creation time. The category is worth noting: it is what the
streamer was broadcasting under at the moment of the clip, which is often a better description
of the content than the clip title.

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.

Endpoints [#endpoints]

<PlatformEndpoints platform="kick" />

Read this before you build [#read-this-before-you-build]

**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](/docs/twitch.md) covers that shape and Kick does not.

**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.

Notes [#notes]

* The endpoint uses `GET` with query parameters
* Authentication via the `x-api-key` header
* Responses follow the unified SocialCrawl schema
* One credit per call
* The URL must be a clip URL (`kick.com/{channel}/clips/{clip_id}`), not a channel or VOD URL