---
search:
  tags:
    - Webhook events
    - POST
    - Webhook
seo:
  description: >-
    A tip went through, but the word filter (or the AI filter) replaced words in
    its… Reference for the POST tip.filtered webhook in the TipPage Developer
    API.
sidebar:
  label: tip.filtered
  badge: POST
title: tip.filtered
type: openapi-operation
---
A tip went through, but the word filter (or the AI filter) replaced words in its name or message before it reached the queue. Unusually for this API, the payload includes the **pre-filter originals** - seeing what was caught is the point of the event. `reasoning` is the AI filter's explanation, when the AI filter made the call.

`POST tip.filtered`

**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.filtered",
  "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",
    "original_name": "string",
    "amount": 0,
    "currency": "string",
    "message": "string",
    "original_message": "string",
    "matched_words": [
      "string"
    ],
    "reasoning": "string"
  }
}
```

**Responses**

- `200` — Return any 2xx quickly.
