---
search:
  tags:
    - Alerts
    - POST
seo:
  description: >-
    Cut the alert the overlay is showing (a gift bomb reading every recipient, a
    long… Reference for the POST /alerts/skip endpoint in the TipPage Developer
    API.
sidebar:
  label: Skip the alert on screen
  badge: POST
title: Skip the alert on screen
type: openapi-operation
---
Cut the alert the overlay is showing (a gift bomb reading every recipient, a long raid). Pass `event_id` to pin the request to THAT alert, so one landing after it ended can't skip the next. The event is marked skipped and never replayed on a reconnect. Requires `tts:control`.

`POST /alerts/skip`

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

- `event_id` (string) — The alert to skip (\`ev\_...\`, from \`/alerts/now\`). Omit to skip whatever is on screen.

Request body example:

```json
{
  "event_id": "string"
}
```

**Responses**

- `200` — Skipped.
- `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\_displaying\` - no alert is on screen, or the one named has already finished. \`skip\_disabled\` - skipping is locked on this channel.
- `429` — Rate limit exceeded - check the \`RateLimit-\*\` headers.

Response example, 200:

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