---
search:
  tags:
    - Webhook events
    - POST
    - Webhook
seo:
  description: >-
    The filter wants to block a tip (a blocked word, or the AI filter's block
    verdict).… Reference for the POST tip.blocked webhook in the TipPage
    Developer API.
sidebar:
  label: tip.blocked
  badge: POST
title: tip.blocked
type: openapi-operation
---
The filter wants to block a tip (a blocked word, or the AI filter's block verdict). The tip is held for a moderator rather than dropped: tip.held follows, and tip.reviewed says whether it was allowed or rejected. The payload carries the original content. A held Stripe payment is only authorised; rejecting it releases the hold.

`POST tip.blocked`

**Webhook.** The API sends this request to your endpoint.

**Payload** (`application/json`)

- `id` (string, required) — Unique event id.
- `type` (any, required)
- `created` (string<date-time>, required)
- `actor` (object | null, required) — Who caused the event. \`null\` for system-originated events (a payment landing, an overlay heartbeat lapsing). Otherwise one of \`user\` (a team member in the dashboard), \`chat\` (a moderator's chat command via the bot), \`api\_key\` (a developer API key), \`oauth\_app\` (an OAuth-connected app), \`overlay\` (the overlay reporting start/finish) or \`bot\`.
- `data` (object, required)

Payload example:

```json
{
  "id": "evt_9f1e2d3c4b5a6978",
  "type": "tip.blocked",
  "created": "2019-08-24T14:15:22Z",
  "actor": {
    "type": "chat",
    "user_id": null,
    "platform": "twitch",
    "platform_id": "123456789",
    "login": "modname",
    "display_name": "ModName"
  },
  "data": {
    "order_id": "string",
    "name": "string",
    "amount": 0,
    "currency": "string",
    "message": "string",
    "blocked_words": [
      "string"
    ],
    "reasoning": "string"
  }
}
```

**Responses**

- `200` — Return any 2xx quickly.
