YouTube Channel Live Videos API

YouTube Channel Live Videos

Features

• Canonical channel URL supportResolve public /@handle, /channel/{id}, /c/{name}, and /user/{name} YouTube URLs.
• Channel live-surface discoveryCollect broadcast entries made available on each submitted channel's live surface.
• Per-channel collection depthRequest 20 to 2,000 records for every input channel, with a default of 100.
• Normalized broadcast recordsReturn video identity, title, description, channel, thumbnail, duration, hashtags, publication time, and source context when available.
• Visible engagement snapshotsCapture public view, like, and comment counts together with collected_at for point-in-time analysis.
• Asynchronous result deliveryPoll task status, retain the task ID, and use cursor pagination for reliable asynchronous result delivery.

Parameters

How to Use

Submit canonical public channel URLs and choose a collection depth for each one. The request creates an asynchronous task, so completion and result retrieval are separate steps.

1. Prepare one or more public YouTube channel URLs using a supported handle, channel ID, custom, or user path.
2. POST urls and results_limit to /v1/youtube/channel-live-videos and retain the returned task_id.
3. Poll /v1/tasks/{task_id} until the task reaches succeeded or failed.
4. Read result pages from /v1/tasks/{task_id}?limit=50 and pass next_cursor back as cursor while has_more is true.

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

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

Best Use Cases

• Broadcast inventory building: Create a structured list of public broadcasts associated with selected channels.
• Livestream programming research: Compare titles, timing, duration, and publishing patterns across channels with recurring live programming.
• Creator broadcast monitoring: Track which public broadcast records are visible on creator, brand, publisher, or competitor channel surfaces.
• Post-broadcast performance snapshots: Store visible views, likes, and comments with collection time for later trend comparisons.
• Public media catalog enrichment: Add normalized broadcast metadata and source-channel context to search, reporting, or classification systems.

Pro Tips

• results_limit applies to every channel. Five URLs with a limit of 100 request up to 500 records before task-wide deduplication.
• Use canonical channel URLs with a non-empty handle, channel ID, custom name, or user name; a bare /channel path cannot resolve a source.
• Treat the channel live surface as the eligibility boundary. Current, upcoming, and archived availability can change between collections.
• Do not infer a reliable current/upcoming/archived state from type or extra.content_type; the normalized payload has no dedicated live-status field.
• The response contains metadata and thumbnail references, not live chat, a playable stream URL, captions, or transcript text.
• Equivalent channel inputs can discover the same video. Saved task results deduplicate by normalized video ID, then by URL when no ID exists.
• Task result limit is separate from results_limit: request 1 to 500 saved rows per page and reuse the opaque next_cursor until has_more is false.
• Public metadata does not unlock private or members-only viewing. Preserve extra.is_members_only when the source reports that classification.

Related APIs