Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.clipping.cc/llms.txt

Use this file to discover all available pages before exploring further.

The starting point of everything is an item — a source you want to monitor.

​
1. Add the item

Post a URL or handle. The API resolves it and creates the item (idempotent per source, so re-posting the same source returns the existing item): 
curl -X POST https://api.clipping.cc/v1/items \
  -H "Authorization: Bearer ck_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "source": "https://youtube.com/@channel" }'

{ "item": { "item_id": "itm_…", "type": "youtube_channel", "name": "…" } }
The type is detected from the source: a channel URL → youtube_channel, a video URL → youtube_video, an RSS feed → rss, etc.

​
2. Sync a channel’s videos

A youtube_channel item fetches its videos one page at a time. Trigger a page sync (channels only) and pass the returned cursor to after for the next page: 
curl -X POST "https://api.clipping.cc/v1/items/itm_123/sync" \
  -H "Authorization: Bearer ck_live_…"
Syncing calls the YouTube API — its real cost is passed through to you. You usually don’t need to sync by hand: a schedule syncs the channels in its collections before each run.

​
3. List the videos

# all videos across your items
curl "https://api.clipping.cc/v1/videos?limit=50" \
  -H "Authorization: Bearer ck_live_…"

# just one channel's videos
curl "https://api.clipping.cc/v1/videos?item_id=itm_123" \
  -H "Authorization: Bearer ck_live_…"
Each video carries its video_id, title, thumbnail URL, the collections it belongs to, and viewer_item_id (your catalogued item for it, if any).

​
4. Inspect the item

GET /v1/items/{id} returns the item with its collections and (for videos) the source channel. List everything you monitor with GET /v1/items (filter by ?type=youtube_channel).

​
Next

Transcribe

Turn a video into searchable text.

Build a reporter

Analyze new videos automatically.