YouTube Playlist Videos API

YouTube Playlist Videos

Features

• Multi-playlist URL and ID inputProcess one or more public playlist URLs or raw playlist IDs in a task, with results_limit applied separately to each resolved playlist.
• Normalized video catalog rowsReturn video IDs, titles, canonical URLs, channel identity, one thumbnail, duration in seconds, and collection time in a consistent structure.
• Playlist and owner provenanceRetain playlist ID, playlist title, readable duration text, and playlist-owner context when a video row does not expose its own channel fields.

Parameters

How to Use

Submit known public playlist references as an asynchronous task, then page through the persisted normalized video rows after the task succeeds.

1. Prepare one or more public playlist URLs containing a list query value or raw playlist IDs, and remove duplicate references.
2. POST urls and an optional results_limit from 10 through 2,000 to /v1/youtube/playlist-videos, then save the returned task_id.
3. Poll /v1/tasks/{task_id} until the task status is succeeded or failed.
4. Read data.results.items and continue with results.next_cursor while results.has_more is true; reconcile playlist IDs and video IDs with your source set.

curl -X POST "https://api.socq.ai/v1/youtube/playlist-videos" \
  -H "Authorization: Bearer $SOCQ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"urls":["https://www.youtube.com/playlist?list=PLP32wGpgzmIlInfgKVFfCwVsxgGqZNIiS"],"results_limit":100}'

# Poll GET /v1/tasks/{task_id}
# Read data.results.items and follow next_cursor while has_more is true

Best Use Cases

• Public playlist inventories: Build a structured inventory of video IDs, titles, URLs, channel identity, thumbnails, duration, and playlist provenance for selected public playlists.
• Course and series indexing: Index playlist titles with their video titles, channel context, durations, and source links to organize public courses, talks, or episodic collections.
• Video enrichment seed lists: Use the returned canonical video URLs and IDs as a deduplicated queue for separate detail, transcript, review, or archival workflows.

Pro Tips

• Use either a raw playlist ID or a URL whose list query value is populated; other URL parts are not used to resolve the playlist and a URL without list is skipped.
• Treat results_limit as a per-playlist ceiling over the first returned video array, not a guarantee of deep extraction for a large playlist.
• Canonicalize each playlist to one representation before batching because only exact duplicate strings are removed and URL variants for the same playlist can trigger repeated work.
• Compare returned extra.playlist_id and video id values with your input set because private, deleted, restricted, hidden, malformed, or unavailable entries can be absent.
• Use collected_at for record lineage and request separate video details when publication dates or engagement are required because metrics is empty and created_at is null.

Related APIs