YouTube Channel Videos API

YouTube Channel Videos

Features

• Multi-channel video collectionCollect regular public videos from multiple channel URLs in one request.
• Per-channel result limitsSet a separate results_limit for each input channel, with a default of 100.
• Normalized video metadataReturn normalized video identity, content metadata, thumbnails, duration, publication date, and publishing channel.
• Point-in-time engagement metricsInclude public view, like, and comment counts with collected_at for later comparison.
• Regular video scopeExclude Shorts and live streams to keep the result focused on regular channel videos.

Parameters

How to Use

Choose how deep to inspect each channel, then collect a clean regular-video inventory. A batch can contain several channels, but the requested limit is applied to each one.

1. Prepare public channel URLs and decide whether you need a recent sample or a deeper backfill.
2. POST urls and results_limit to /v1/youtube/channel-videos; remember that the limit applies per channel.
3. Poll /v1/tasks/{task_id} until the inventory task reaches succeeded or failed.
4. Group returned items by channel ID, deduplicate by video ID, and paginate while has_more is true.

curl -X POST "https://api.socq.ai/v1/youtube/channel-videos" \
  -H "Authorization: Bearer $SOCQ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"urls":["https://www.youtube.com/@NASA"],"results_limit":10}'

# Poll GET /v1/tasks/{task_id}
# Read GET /v1/tasks/{task_id}?limit=50

Best Use Cases

• Channel content feeds: Build a structured feed of regular public videos from selected channels.
• Publishing and performance analysis: Compare publication frequency, duration, topics, and public engagement across channels.
• Creator and competitor monitoring: Track regular video activity from creators, publishers, brands, or competitors.
• Video catalog creation: Populate classification, summarization, search, or reporting workflows without collecting each video URL manually.

Pro Tips

• The limit multiplies across inputs. Ten channels with results_limit 100 request up to 1,000 regular-video records.
• Start shallow when onboarding a new channel set, inspect eligibility, then raise the limit only where deeper history is useful.
• Fewer results can mean the channel has fewer eligible public uploads. It does not automatically indicate a failed task.
• Do not present the response as a guaranteed complete archive; availability and public channel inventory can change.
• Use video ID for deduplication and retain both the source channel ID and collected_at for longitudinal analysis.
• Run Shorts separately if format mix matters. Combining the two only after collection keeps classification explicit.
• Use Channels for current profile fields rather than copying channel bios and counters into every upload row.

Related APIs