ClippedDocs

Clipped API

Watch streamers, read the clips Clipped cuts from their streams, and post the good ones. From a script, from your own server, or from an AI agent over MCP.

Base addresshttps://app.clipped.so/api/v1
AuthenticationAuthorization: Bearer clip_sk_…
Get an API keyQuickstart
Your first callShell
curl https://app.clipped.so/api/v1/me \
  -H "Authorization: Bearer clip_sk_…"

What you can build

Each of these is a short walk through the calls it takes, with code to copy.

Hands-off channelPost a streamer's best clips automaticallyWatch a streamer, set a score to post from, and let Clipped put the standouts on YouTube with nobody at a keyboard.Gallery or dashboardShow new clips in your own appPoll the clip feed with a cursor, keep every clip with its thumbnail, and play the video through your own server.Event-driven backendBe told the moment a clip is readyHave Clipped POST to your server when a clip is found, when one is posted, and when a streamer goes live or offline.Editor in the loopPick the clips yourself, then post themList what was found, look at the ones worth looking at, and post the keepers to YouTube, TikTok or Instagram with your own titles.Overlays, alerts, researchReact to a stream while it is liveFollow a streamer's hype score, transcript and chat second by second over a WebSocket, and hear about clips the instant they are found.No codeHand it to an AI agentConnect Claude, or any MCP client, and ask in plain words: find streams, follow streamers, set rules, read clips and post them.ReportingSee which clips are workingRead views, likes and comments for everything you posted, per streamer, site, game and kind of clip, and feed it back into your rules.

The API, by what it works on

23 endpoints. See them all on one page.

Streamers

GET/api/v1/streamersWho you are watching.POST/api/v1/streamersStart watching one.GET/api/v1/streamers/{channel}One streamer: live or not, and their rules.PATCH/api/v1/streamers/{channel}Give them rules of their own.DELETE/api/v1/streamers/{channel}Stop watching one.

Settings

GET/api/v1/settingsEvery setting, and which accounts are connected where.PATCH/api/v1/settingsChange some of them.

Clips

GET/api/v1/clipsClips, oldest first.GET/api/v1/clips/{id}One clip.GET/api/v1/clips/{id}/videoThe mp4.GET/api/v1/clips/{id}/thumbnailIts thumbnail.

Posting a clip

POST/api/v1/clips/{id}/publishPost it.

Updates and webhooks

GET/api/v1/webhooksYour webhooks, and each one's last delivery.POST/api/v1/webhooksMake one.PATCH/api/v1/webhooks/{id}Change one, or switch it back on.POST/api/v1/webhooks/{id}/testSend it a ping now.DELETE/api/v1/webhooks/{id}Delete one.

Live feeds

GET/api/v1/streamsEach streamer you follow, whether a recording of them is running, and their three feed addresses.WS/api/v1/streams/{channel}/analysisThe signals, second by second, and the clips found.WS/api/v1/streams/{channel}/transcriptWhat the streamer says, a segment at a time, with each word's timing.WS/api/v1/streams/{channel}/chatEvery chat message, and each one's score once it has one.

Analytics

GET/api/v1/analytics?days= 1–365 (28 by default), ?channel= for one streamer. Answers { report, reflections }.

How it fits together

  1. You watch a streamer. Clipped records them whenever they go live. Streamers
  2. Clipped finds the moments. Each gets a score from 0 to 100, a title and a thumbnail. Clips
  3. You hear about them. Poll with a cursor, take a webhook, or follow the stream live. Webhooks · Live feeds
  4. The good ones are posted. By a rule you set, or by a call you make. Auto-posting · Posting a clip

For agents

Clipped is an MCP server: point an agent at https://app.clipped.so/api/mcp with a key and it can do all of the above. These docs are also one plain file, at /llms.txt.