Webhook
Send audit logs to any HTTP endpoint for custom processing.
Prerequisites
- An HTTP(S) endpoint that accepts POST requests with JSON payloads.
- Network connectivity from your deployment to the webhook URL.
Configuration fields
| Field | Required | Description |
|---|---|---|
| URL | Yes | The full webhook URL (e.g., https://api.example.com/logs). |
| Headers | No | Extra headers sent with every request, as name and value pairs. Use this for auth, e.g. Authorization with Bearer <token>, or an API key header such as X-API-Key. Values are masked in the form like other provider credentials. |
| Anonymous Mode | No | Toggle to send only statistical data (see Anonymous Mode). |
How it works
Each audit log is sent as a POST request with the following JSON structure:
{
"timestamp": "2024-01-15T10:30:00.000Z",
"type": "audit_log",
"data": { ... }
}
The Content-Type header is set to application/json, and any headers you configure are added to it. Host, Content-Length, Transfer-Encoding, and Connection are set by Willow and can't be overridden. The request timeout is 5 seconds.
Authenticate requests
Select Add header to attach a header to every request. The first header you add is prefilled with the name Authorization. For a Bearer token, set its value to Bearer <token>:
| Name | Value |
|---|---|
Authorization | Bearer eyJhbGciOi… |
Header names may contain letters, digits, and -. A row with both fields empty is ignored.
See Log schemas for the fields in data for each event type.
Tips
- Implement idempotency on your receiver to handle potential retries.
- Protect your endpoint with an auth header (see Authenticate requests) and reject requests that don't carry it.
- Use this for custom pipelines, SIEM integrations, or forwarding to collectors not natively supported.
Troubleshooting
- Confirm your endpoint returns a 2xx status code.
- 401 / 403 responses: check the header name and value match what your endpoint expects, including the
Bearerprefix if it needs one. - Requests time out after 5 seconds.
If no logs appear at all, confirm the provider credentials and URL are correct and that outbound egress is allowed. See Log Settings for shared guidance.
Related
- Log Settings: retention, content options, and Anonymous Mode
- Logs: view and search the logs themselves