---
search:
  tags:
    - TTS queue
    - POST
seo:
  description: >-
    Pass order_id to pin the request to THAT tip, so a request that lands after
    it has… Reference for the POST /tts/skip endpoint in the TipPage Developer
    API.
sidebar:
  label: Skip the currently-playing TTS
  badge: POST
title: Skip the currently-playing TTS
type: openapi-operation
---
Pass `order_id` to pin the request to THAT tip, so a request that lands after it has already finished can't skip the next one; omit it to skip whatever is playing. In linked mode the unit (TTS and media) is skipped together. Requires `tts:control`.

`POST /tts/skip`

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

- `order_id` (string) — The tip to skip (from \`/tts/now\`). Omit to skip whatever is playing.

Request body example:

```json
{
  "order_id": "string"
}
```

**Responses**

- `200` — Skipped (a no-op when nothing was playing and no \`order\_id\` was given).
- `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\`).
- `409` — \`not\_playing\` - the \`order\_id\` named has already finished (\`current\_order\_id\` says what is playing now, or null). \`skip\_disabled\` - skipping is locked on this channel.
- `429` — Rate limit exceeded - check the \`RateLimit-\*\` headers.

Response example, 200:

```json
{
  "success": true,
  "skipped_order_id": "string"
}
```
