YouTube Community Posts API

YouTube Community Posts

Features

• Multi-channel URL collectionAccept complete public channel URLs using @handle, /channel/, /c/, or /user/ paths and apply the selected result ceiling independently to each channel.
• Normalized post recordsReturn public post IDs, Community URLs, text, publication timestamps, and collection timestamps in a consistent structure.
• Channel-to-post contextKeep each post connected to its channel ID, handle, display name, public channel URL, and submitted source URL.
• Image attachment referencesMap exposed post images into normalized media entries so image-based updates remain connected to their post records.
• Bounded feed traversalFollow source continuation pages per channel, remove duplicate posts by ID or URL, and stop at the selected limit, feed end, or 100-page ceiling.

Parameters

How to Use

Submit one or more known public channels as an asynchronous task, then read the saved Community post records after completion.

1. Prepare complete public YouTube channel URLs using an @handle, /channel/, /c/, or /user/ path.
2. POST urls and a results_limit from 20 through 2000 to /v1/youtube/community-posts.
3. Retain the returned task_id and poll GET /v1/tasks/{task_id} while the task is queued, running, or retrying.
4. After success, read data.results.items and pass data.results.next_cursor as cursor on the task request while data.results.has_more is true.

curl -X POST "https://api.socq.ai/v1/youtube/community-posts" \
  -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 data.results.items and pass data.results.next_cursor as cursor while has_more is true

Best Use Cases

• Channel Community feed inventory: Use post IDs, URLs, text, timestamps, and source-channel context to build a reviewable feed from selected public channels.
• Announcement and creative review: Review public post text alongside retained image references to compare how channels present updates outside their video feeds.
• Cross-channel publishing analysis: Group normalized posts by channel identity and publication time to compare Community posting activity across a known channel set.

Pro Tips

• Submit a complete channel URL on a supported YouTube host; video, post, playlist, and bare non-URL values fail the public channel-input contract.
• Size multi-channel requests deliberately because results_limit applies to every URL: three channels at 20 can request up to 60 saved posts.
• Treat results_limit as a ceiling, since a channel without a public Community tab or with a shorter visible feed can return fewer records.
• Use cursor only with GET /v1/tasks/{task_id}; source continuation is handled internally and is not a public request parameter for this endpoint.
• Deduplicate stored records by post ID, falling back to URL, and retain extra.input_url when several submitted channels are combined.
• Check text, media, and created_at before downstream use; current normalized records do not retain poll choices or embedded-video attachment metadata.

Related APIs