# YouTube Channel Community Posts API (https://www.socialcrawl.dev/platforms/youtube/channel-community-posts)

> Fetches community posts from a YouTube channel's Posts tab (post ID, URL, content, images, attached video, like count, publish time, channel info) plus a `continuationToken` when more results are available. Pass `handle` or `channelId` for the first page; forward `continuationToken` for subsequent pages. DATES ARE APPROXIMATE: `post.published_at` is derived from the tab's own relative label ("2 days ago"), so its time-of-day is not real and the date is only as precise as that label. This tab publishes no exact timestamp.

TL;DR: `GET /v1/youtube/channel/community-posts` costs 1 credit per call and returns SocialCrawl's unified JSON schema. Single x-api-key auth, 100 free credits on signup.

## Parameters

| Parameter | Required | Description |
| --- | --- | --- |
| `channelId` | no | YouTube channel ID. |
| `handle` | no | YouTube channel handle (with or without @). |
| `continuationToken` | no | Continuation token from a previous response: fetches the next page. |
| `since` | no | Only rows published on or after this date: YYYY-MM-DD (midnight UTC) or an ISO 8601 timestamp. Rows older than it are left off each page. This list is not in date order, so the walk does not stop at the date: keep following `next_cursor`, and each page costs what a page costs even when every row on it is filtered out. A row with no date is kept. `published_after`, `start_date`, `from_date`, `publish_time` (`yesterday`, `this-week`, `this-month`, `last-3-months`, `last-6-months`) and `max_age_days` are accepted and applied as `since`. |
| `until` | no | Only rows published on or before this date: YYYY-MM-DD (that whole UTC day is included) or an ISO 8601 timestamp. Newer rows are left off each page and the walk does not stop, so older pages follow. A row with no date is kept. `published_before`, `end_date` and `to_date` are accepted and applied as `until`. |
| `max_pages` | no | 1 to 50 (default 1, or 50 when `max_items` or `max_credits` is sent). Walk up to this many pages in one call and return the rows from all of them. Each page walked is billed exactly as one call to this endpoint (a cached page is free) and counts against your rate limit; its charge and any refund are recorded under the page's own request id, listed in `data.walk.request_ids`. The walk stops early at the last page, or when the request's time budget runs low; `data.walk.stopped` says why (`end`, `max_pages`, `max_items`, `max_credits`, `time_budget`, `page_error`) and `pagination.next_cursor` continues from where it stopped. |
| `max_items` | no | 1 to 5000. Get more in one call: keep walking pages until the response holds at least this many rows, then stop with `data.walk.stopped: "max_items"`. The last page is returned whole (it was billed), so `data.items` can hold up to one page more than this, and `pagination.next_cursor` resumes right after it without skipping a row. Walks up to 50 pages unless `max_pages` says fewer; each page is billed as one call (a cached page is free). Add `max_credits` to cap the spend. A long walk can stop on the time budget first (`"time_budget"`): send the returned cursor with the same params to continue. |
| `max_credits` | no | 1 to 100000. The most this call may spend, across every page it walks. A page starts only while the credits already spent plus that page's price (or, when higher, the most any page of this walk has cost) still fit, so the call never goes past it; the walk then stops with `data.walk.stopped: "max_credits"` and the cursor to resume. Sent alone, it walks as far as the budget goes (up to 50 pages). A value below the price of one page is a free 400 whose `error.details.page_credits` names that price. Credits a row join (`include=`) adds are known only once a page has run, so page 1 is checked against its own price. |

## Code example

```bash
curl -G "https://www.socialcrawl.dev/v1/youtube/channel/community-posts" \
  --data-urlencode "handle=MrBeast" \
  -H "x-api-key: sc_YOUR_API_KEY"
```

## FAQ

### How do I fetch a channel's YouTube community posts?

Send a GET to /v1/youtube/channel/community-posts with a handle or channelId. The response lists posts with ID, text content, images, any attached video, like count, and publish time.

### What is a YouTube community post?

Community posts are the text, image, and poll updates a channel shares on its Posts tab, separate from its videos. This endpoint reads that tab for any public channel.

### Do I pass a handle or a channel ID?

Either one. Provide handle (with or without @) or channelId for the first page; exactly one of the two is required.

### How do I page through all community posts?

Each response includes a continuationToken when more results exist. Forward it as continuationToken=... on the next request and repeat until it is empty.

### How much does the community posts endpoint cost?

It is a standard endpoint at 1 credit per request, and new accounts start with 100 free credits to test it.

See the full YouTube API: https://www.socialcrawl.dev/platforms/youtube

## Pricing

- Standard endpoints: 1 credit per call
- Advanced endpoints: 5 credits per call
- Premium endpoints: 10 credits per call
- 100 free credits on signup, no credit card required. Cached responses cost 0 credits. Credit packs never expire.
- Full pricing: https://www.socialcrawl.dev/pricing

## Explore with AI

Questions this API answers, phrased for an AI assistant:

- How to fetch YouTube community posts from a channel via API
- YouTube community tab API without Data API quota