---
search:
  tags:
    - TTS queue
    - POST
seo:
  description: >-
    Re-queues a played tip (as a new queue entry with a fresh replay_...…
    Reference for the POST /tts/{orderId}/replay endpoint in the TipPage
    Developer API.
sidebar:
  label: Replay a TTS from history
  badge: POST
title: Replay a TTS from history
type: openapi-operation
---
Re-queues a played tip (as a new queue entry with a fresh `replay_...` order id; fires `tip.created` with `source: "replay"`). A short idempotency window returns `409` if the same tip was just replayed. Requires `tts:control`.

`POST /tts/{orderId}/replay`

**Responses**

- `200` — Done.
- `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` — Replayed too recently (idempotency window).
- `429` — Rate limit exceeded - check the \`RateLimit-\*\` headers.

Response example, 200:

```json
{
  "success": true
}
```
