> For the complete documentation index, see [llms.txt](https://docs.rad.live/rad/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rad.live/rad/rad-tv-developer-api/graphql/queries.md).

# Queries

All queries are executed via `POST /graphql` with a JSON body. Most require `Authorization: Bearer <token>`.

## Query list

| Query                                        | Auth   | Description                                                                                                  |
| -------------------------------------------- | ------ | ------------------------------------------------------------------------------------------------------------ |
| `me`                                         | yes    | Current user (channel, followedChannels, ingestions, youtube, profile, subscription, credits, media, wallet) |
| `channel(id: DID!)`                          | yes    | Single channel by DID (null if not found)                                                                    |
| `channels(limit, start)`                     | yes    | All channels (paginated)                                                                                     |
| `categories(limit, start)`                   | yes    | All categories (paginated)                                                                                   |
| `ratings(limit, start)`                      | **no** | All content ratings (e.g. MPAA, TV); public                                                                  |
| `genres(limit, start)`                       | **no** | All content genres; public                                                                                   |
| `comments(contentId, limit, start)`          | yes    | Comments for content by DID                                                                                  |
| `stream(id)` / `streams(limit, start)`       | yes    | Single stream or list (catalog)                                                                              |
| `episode(id)` / `episodes(limit, start)`     | yes    | Single episode or list (catalog)                                                                             |
| `miniserie(id)` / `miniseries(limit, start)` | yes    | Single miniserie or list (catalog)                                                                           |
| `season(id)` / `seasons(limit, start)`       | yes    | Single season or list (catalog)                                                                              |
| `serie(id)` / `series(limit, start)`         | yes    | Single serie (TV series) or list (catalog)                                                                   |
| `feature(id)` / `features(limit, start)`     | yes    | Single feature (content) or list (catalog)                                                                   |
| `youtubeVideos(pageToken, limit)`            | yes    | User's YouTube videos (requires connected account)                                                           |
| `youtubePublishJob(id)`                      | yes    | Status of a YouTube publish job                                                                              |

{% hint style="info" %}
Pagination: List queries accept `limit` and `start` (e.g. `channels(limit: 20, start: 0)`). There is no cursor-based pagination in the schema; use `start` as an offset for the next page.
{% endhint %}

## Single-entity queries

`channel(id)`, `feature(id)`, `stream(id)`, `episode(id)`, `miniserie(id)`, `season(id)`, `serie(id)`, and `youtubePublishJob(id)` return a single object or **null** when the entity is not found or not accessible. Check for null before using the result.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.rad.live/rad/rad-tv-developer-api/graphql/queries.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.