---
search:
  tags:
    - Alerts
    - POST
seo:
  description: >-
    Play an alert again through the connected overlay's alert box, exactly like…
    Reference for the POST /alerts/{id}/replay endpoint in the TipPage Developer
    API.
sidebar:
  label: Replay an alert from the history
  badge: POST
title: Replay an alert from the history
type: openapi-operation
---
Play an alert again through the connected overlay's alert box, exactly like the original: a new event (`event_id`) with `replay_of` set, marked as a replay on screen. No webhook, no sub-reward credit, no chat announce, no filter run. With no overlay connected the replay is parked (`parked: true`) and plays on the next connect. Requires `tts:control`.

`POST /alerts/{id}/replay`

**Responses**

- `200` — Replaying (or parked).
- `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 alert in the history.
- `409` — \`overlay\_wont\_show\` - the connected overlay's alert box would not show it (\`reason\` = type\_off | platform\_off | under\_minimum | reward\_not\_listed, \`overlay\` names it). \`blocked\` - the original was blocked by the tip filter.
- `429` — Rate limit exceeded - check the \`RateLimit-\*\` headers.

Response example, 200:

```json
{
  "success": true,
  "event_id": "string",
  "replay_of": "string",
  "parked": true,
  "overlay": {}
}
```
