# Custom responses

Override the status code, content type and body that Webhooker returns to the sender after a successful ingest.

Source: https://docs.webhooker.eu/receive/custom-response/

By default a successful ingest answers `200` with a small JSON body. Some
senders insist on something else: a bare `204`, a plain-text token, a
provider-specific acknowledgement. Configure it per source under **Settings →
Enable custom response**.

## Fields

| Field | Values |
| --- | --- |
| **Status code** | Any valid HTTP status, 100 to 599. |
| **Content type** | JSON or plain text. |
| **Response body** | Sent verbatim. |

The body supports one placeholder: `{{request_id}}`, replaced with the stored
event id.

```json
{ "received": "{{request_id}}" }
```

## Notes

- The override applies to accepted events only. Verification failures, rate
  limits and quota errors keep their own status codes and error bodies, so your
  monitoring still sees real failures as failures.
- A sender that treats anything other than `200` as an error — or the reverse —
  is the main reason to touch this. If your sender is happy, leave it off.
- Turning the override off restores the default JSON acknowledgement.