# YouTube

> Read public YouTube channels, videos, playlists, comments, and transcripts.

Source page: https://docs.replynodes.com/docs/guides/youtube

# YouTube

The `youtube` tag exposes read operations for search, channels, videos, playlists, related videos, comments, and transcripts. Paths include `/v1/youtube/search`, `/v1/youtube/channel/{id}`, `/v1/youtube/video/{id}`, `/v1/youtube/playlist/{id}`, `/v1/youtube/related/{id}`, `/v1/youtube/comments/{id}`, and `/v1/youtube/transcript/{id}`. Use the [API Reference](https://docs.replynodes.com/reference) for required identifiers and optional language/limit parameters.

## Choose an operation

Use `GET /v1/youtube/search` with `term` to search public YouTube data. Its optional parameters are `language` and `limit`. When you have an identifier, use `GET /v1/youtube/video/{id}`, `GET /v1/youtube/channel/{id}`, or `GET /v1/youtube/playlist/{id}`. Each path takes `id`; video, channel, and playlist reads also accept `language`.

To continue from a video, `GET /v1/youtube/related/{id}` reads related videos and accepts `language`. `GET /v1/youtube/comments/{id}` reads comments and accepts `limit`. `GET /v1/youtube/transcript/{id}` reads a transcript and accepts `language`. These operations read public data only. Use the generated API Reference for the response schema and the contract-defined fields returned by each operation.

## Make a request

Keep the API key server-side or in your client’s secret mechanism. This example searches using a term:

```bash
curl -sS \
  -H "Authorization: Bearer $REPLYNODES_API_KEY" \
  "https://api.replynodes.com/v1/youtube/search?term=web%20context"
```

Successful responses use the `{ data, meta }` envelope. Keep `meta.request_id` when diagnosing a request. See [Quickstart](https://docs.replynodes.com/docs/quickstart) for the common HTTP setup, [Reddit](https://docs.replynodes.com/docs/guides/reddit) for another public-data guide, and the [API Reference](https://docs.replynodes.com/reference) for operation parameters.

Start with search when the agent has a topic or phrase, or begin with a channel, video, or playlist identifier when the source is already known. Use related videos and comments as targeted enrichment steps rather than as an unbounded crawl. Transcript requests may depend on the video's available languages, so keep the requested language and the selected video identifier with the result. Public metadata, comments, and transcripts can change or disappear upstream; record the retrieval time and treat the response as an observation of the public surface at that moment.

Every operation is a read-only `GET` request. The [API Reference](https://docs.replynodes.com/reference) defines exact identifiers, optional limits, language parameters, pagination, and response fields; do not infer an undocumented route from a provider URL. Preserve `request_id` values and use bounded retries for safe transient reads. Honor `Retry-After` on `429` responses and do not send credentials, cookies, or private-session data to this public provider surface. If a requested item is unavailable, report the upstream limitation instead of silently substituting a different video or channel.