---
search:
  tags:
    - Media queue
    - POST
seo:
  description: >-
    Put a video straight into the media queue, no tip attached - it plays on the
    overlay… Reference for the POST /media endpoint in the TipPage Developer
    API.
sidebar:
  label: Queue a video
  badge: POST
title: Queue a video
type: openapi-operation
---
Put a video straight into the media queue, no tip attached - it plays on the overlay through the normal queue like any other request. The URL goes through the same validation as every entry route: platform parsing, playability checks, and the streamer's banned-videos list. Queued items carry `requested_via: "api"` and fire the `media.created` webhook. Requires `media:control`.

`POST /media`

**Request body** (`application/json`, required)

- `url` (string<uri>, required) — The video URL (YouTube and other supported platforms).
- `start_time` (integer) — Start offset in seconds.
- `name` (string) — Display name shown in the queue ("requested by").

Request body example:

```json
{
  "url": "http://example.com",
  "start_time": 0,
  "name": "API"
}
```

**Responses**

- `201` — Queued.
- `400` — Invalid, unplayable, or banned video (\`invalid\_media\`), or missing url (\`bad\_request\`).
- `401` — Missing or invalid credential (\`missing\_api\_key\` / \`invalid\_api\_key\`, or \`invalid\_token\` for an expired/revoked OAuth access token).
- `403` — The key lacks the required scope (\`missing\_scope\`).
- `429` — Rate limit exceeded - check the \`RateLimit-\*\` headers.

Response example, 201:

```json
{
  "media": {
    "order_id": "string",
    "donor_name": "string",
    "media_url": "http://example.com",
    "media_start_time": 0,
    "video_title": "string",
    "video_thumbnail": "http://example.com",
    "video_duration": 0,
    "platform": "youtube",
    "requested_via": "string",
    "is_replay": true,
    "queued_at": "2019-08-24T14:15:22Z"
  }
}
```
