---
search:
  tags:
    - TTS queue
    - POST
seo:
  description: >-
    Marks a queued TTS as currently playing - the same call the overlay makes.…
    Reference for the POST /tts/{orderId}/start endpoint in the TipPage
    Developer API.
sidebar:
  label: Claim a TTS as now playing
  badge: POST
title: Claim a TTS as now playing
type: openapi-operation
---
Marks a queued TTS as currently playing - the same call the overlay makes. Fires `queue.tts.started`. While claimed, other consumers get `409 already_playing`. If your effect then fails and the tip should not count as played, undo the claim with [release](/api/reference/tts-queue/releasettsitem) instead of finishing. See the [claim, do your thing, finish](https://docs.tippage.com/api/claim-and-finish) guide for the full pattern. Requires `tts:control`.

`POST /tts/{orderId}/start`

**Responses**

- `200` — Claimed.
- `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\`).
- `404` — No such resource.
- `409` — \`queue\_paused\` (the queue is paused) or \`already\_playing\` (another tip holds the slot; \`current\_order\_id\` names it).
- `429` — Rate limit exceeded - check the \`RateLimit-\*\` headers.

Response example, 200:

```json
{
  "success": true,
  "tip": {
    "order_id": "tip_1755100000000_ab12cd",
    "name": "string",
    "amount": 5,
    "message": "string",
    "tts_url": "http://example.com",
    "is_replay": true,
    "is_sub_reward": true,
    "source": "string",
    "external_source": "string",
    "external_ref": "string",
    "is_paid": true,
    "platform": "twitch",
    "platform_user_id": "string",
    "name_was_filtered": true,
    "message_was_filtered": true,
    "queued_at": "2019-08-24T14:15:22Z"
  }
}
```
