Aggregate webhook delivery view across all tenant endpoints

Recent delivery attempts across all the tenant’s webhook endpoints…

GET /api/v1/webhooks/deliveries/recent

cURL

curl --request GET \
  --url 'https://api.computer.stateset.app/api/v1/webhooks/deliveries/recent' \
  --header "X-API-Key: $STATESET_COMPUTER_USE_API_KEY"

200

[
  {
    "id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
    "endpoint_id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
    "event_type": "string",
    "status": "pending",
    "response_code": 1,
    "attempts": 1,
    "next_retry_at": "2026-08-31T14:22:05Z",
    "created_at": "2026-08-31T14:22:05Z"
  }
]

Recent delivery attempts across all the tenant’s webhook endpoints.

Per-endpoint history sits at /webhooks/{id}/deliveries — this is the dashboard view: ‘show me what every webhook fired in the last N attempts, regardless of which endpoint.’ Sorted newest-first. Cross-tenant leakage prevented by joining through WebhookEndpoint.

Pagination. Two modes:

• Bare ?limit=N returns the N newest rows, with X-Next-Cursor set when the result fills the page (more rows exist).
• Pass ?cursor=<value> to page strictly past the seed — receives only rows strictly older than the cursor’s created_at (ties broken by id for determinism). Mirror of the cursor pattern on /jobs.

Query parameters

limit · integer

status · string,null

Filter to one of: pending, success, failed.

cursor · string,null

Opaque cursor from a previous response’s X-Next-Cursor header. When supplied, pages strictly past the seed row using a seek predicate — stable across new deliveries arriving mid-paginate (offset would skip rows; cursor won’t). Format is the prior page’s last delivery id.

Response

WebhookDeliverySummary[] — each element:

id · string · required

endpoint_id · string · required

event_type · string · required

status · string · required

pending | success | failed

response_code · integer,null

HTTP status from the receiver, if a response was received.

attempts · integer · required

Total attempts so far (1..3).

next_retry_at · string,null

Scheduled retry time, ISO 8601 UTC, when status == ‘failed’.

created_at · string · required

Status codes

Code	Meaning
200	Successful Response
422	Validation Error

cURL

curl --request GET \
  --url 'https://api.computer.stateset.app/api/v1/webhooks/deliveries/recent' \
  --header "X-API-Key: $STATESET_COMPUTER_USE_API_KEY"

200

[
  {
    "id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
    "endpoint_id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
    "event_type": "string",
    "status": "pending",
    "response_code": 1,
    "attempts": 1,
    "next_retry_at": "2026-08-31T14:22:05Z",
    "created_at": "2026-08-31T14:22:05Z"
  }
]