Retrieve a list of events received by a specific webhook by providing its 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.
Path Parameters
id string
The unique ID of the webhook for which events are being retrieved. Example: 'c03b02ec-244f-4d2c-8f68-3910071ed5c8'
Query Parameters
limit (optional) positive integer
Specifies the maximum number of webhook events to return, such as '10'. You can choose to include this parameter as needed.
ResponseThis section is used to view the possible HTTP response codes returned by the API. These codes indicate the status of a request, such as 201 (Created), 401 (Unauthorized), 409 (Conflict), or 422 (Unprocessable Entity).