webhook_id
in the path. Each event represents a payload submitted to the webhook endpoint — typically from an external system or alerting service.The response includes metadata such as the
content_type
of the payload, the raw body
of the received request, the sender’s IP address
, and the received_at
timestamp.You can use query parameters like
last_received_at
and limit
to paginate results and retrieve only the most recent entries.Use cases:
- Integration troubleshooting — View the actual payloads and metadata received to debug malformed requests or failures.
- Webhook activity audit — Track which external systems have submitted events and when.
- Payload inspection — Validate the structure and content of incoming webhook data before mapping it to rulesets.
To view all available webhook endpoints in your system, see Get Webhooks.
Authorization: Bearer YOUR_TOKEN
Expected Behavior:
- On success, the system will return webhook event details such as content type, body, IP, and received time.
- If the request is unauthorized, the system will return an authentication error message.