> **For coding agents and LLMs:** This is one Social Fetch marketing page (markdown export). For API orientation start with [`/llms.txt`](https://www.socialfetch.dev/llms.txt); for auth and crawl rules use [`/agents.txt`](https://www.socialfetch.dev/agents.txt); for every operation use [`/llms-endpoints.txt`](https://www.socialfetch.dev/llms-endpoints.txt).

## This page

- **On-site (HTML):** <https://www.socialfetch.dev/platforms/youtube/community-posts>
- **Markdown (.mdx) URL:** <https://www.socialfetch.dev/platforms/youtube/community-posts.mdx>

---

# YouTube Community Post API

Resolve a public youtube.com/post URL into post text, attached images or linked video, channel identity, and like count.

`GET /v1/youtube/community-posts` takes a required `url` query param pointing at a public community post (typically `https://www.youtube.com/post/...`). On a found lookup you get `data.post` (id, canonical url, text, publishedAt, publishedTimeText), `data.channel` (platformUserId, handle, displayName, profileUrl), `data.media` (`imageUrls` plus optional `linkedVideo` with id, title, thumbnail, views, and duration), and `data.metrics.likes`. Branch on `data.lookupStatus` before you write rows — HTTP 200 alone does not mean the post resolved.

Bill from `meta.creditsCharged`. This route is one post by URL. Channel identity is `GET /v1/youtube/channel`. A watch URL is `GET /v1/youtube/videos`.

## Request

- **Endpoint:** `GET /v1/youtube/community-posts`
- **Credits:** 1 credit
Failed requests are free
- **Input:** by URL
- **Full reference:** [docs](https://www.socialfetch.dev/docs/api/v1/youtube/community-posts/get)
- **Platform page:** [/platforms/youtube](https://www.socialfetch.dev/platforms/youtube)

## FAQ

### How do I get a YouTube community post via API?

Call GET /v1/youtube/community-posts with your Social Fetch API key (x-api-key) and a public community post url query param. Read data.lookupStatus, then data.post, data.channel, data.media, and data.metrics. See the API docs for parameters and examples.

### How much does the YouTube Community Post API cost?

Pricing is documented on the operation in the API registry (shown on this page). Confirm on every response with meta.creditsCharged — that field is the billing source of truth.

### What URL format does this endpoint accept?

A public YouTube community post URL, typically https://www.youtube.com/post/{postId}. Pass one url per request. Watch URLs and channel URLs belong on other YouTube routes.

### What does the community post response include?

When found: data.post (id, url, text, publishedAt, publishedTimeText), data.channel (handle, displayName, profileUrl, platformUserId), data.media.imageUrls, optional data.media.linkedVideo, and data.metrics.likes. Always branch on data.lookupStatus first.

### Does a completed request always mean the post was found?

No. HTTP 200 means the request finished. Check data.lookupStatus: found means you got post details; not_found means the URL did not resolve. Persist meta.requestId when you need to debug a miss.

### Can community posts include images or a linked video?

Yes. data.media.imageUrls lists attached image URLs when present. data.media.linkedVideo is set when the post embeds or promotes a video, with id, url, title, thumbnail, view counts, and duration fields when available.

### How is this different from GET /v1/youtube/videos?

This route resolves a community post URL into post text, images, and likes. GET /v1/youtube/videos resolves a watch (or Shorts) URL into video metadata, chapters, and engagement. Use community-posts for /post/ links; use videos for watch links.

### Do I need a Google Cloud project for this endpoint?

No. You authenticate to Social Fetch with an API key. The route reads public community post data; it does not act on behalf of a logged-in YouTube user.