Delivery Logs
Every webhook delivery attempt is recorded. View the history from the dashboard or via the API to diagnose delivery issues and replay failed events.
Accessing logs
- Dashboard: Developers → Webhooks → [Endpoint] → Logs.
- API:
GET /webhooks/{id}/deliveries/. - Available filters: status (
succeeded/failed), event type, time period.
Available fields per attempt
| Field | Description |
|---|---|
id | Unique identifier of the delivery attempt. |
event_type | Type of delivered event. |
event_id | Identifier of the source event. |
status | succeeded or failed. |
http_status_code | HTTP status code returned by your endpoint. |
response_time_ms | Response time from your endpoint (ms). |
attempt_count | Attempt number (1, 2, 3…). |
next_retry_at | Date of the next attempt if failed. |
created_at | Timestamp of the attempt. |
Replay a failed delivery
From a failed log entry in the dashboard, click Replay to immediately
trigger a new attempt without waiting for the next automatic retry cycle. You can also
do this via the API: POST /webhooks/{id}/deliveries/{did}/retry/.
Debugging a 500 error
If your endpoint consistently returns 500, first check your
server’s application logs. The response_time_ms field tells
you whether it’s a timeout (close to 30,000 ms) or a fast application error. Fix your
code, then replay the delivery.
Are the delivery logs well documented?
Object schema
ResponseGET /webhooks/{id}/deliveries/
Paginated list of delivery attempts for a given endpoint.
Replay a delivery (API)
Response200 OK — Delivery replayed
Sangho immediately sends a new attempt to your endpoint.