Delivery History

View every delivery attempt with status, HTTP codes, and timing, inspect request and response bodies, replay failed attempts, and clear the delivery log.

The delivery history tracks every attempt to deliver a payload to a destination. Each attempt is recorded as a delivery item with status, timing, HTTP response code, and optional request/response bodies. Use this endpoint to audit delivery performance and debug failures.

Query items by binding_id or destination_id to narrow results to a specific delivery path. Filter by status to find failures (failed) or in-progress attempts (in_flight). Use GET /v1/delivery/items/:id to inspect the full request and response bodies for a single attempt.

Each item includes an idempotency_key (deterministic SHA-256 of binding ID and event ID) that is sent on the wire so receivers can deduplicate. The attempt field is 1-indexed — multiple items with the same event_id and binding_id represent retries of the same delivery. Status values are in_flight, succeeded, or failed.

Use POST /v1/delivery/items/:id/replay to re-enqueue a specific attempt with a fresh attempt number but the same idempotency key. For terminal failures, check the DLQ endpoint instead — items that exhausted all retries are moved there automatically. Pair history inspection with binding and destination detail to diagnose delivery issues end-to-end.

Response

{
  "items": [
    {
      "id": "e5f6a7b8-c9d0-1234-efab-456789012345",
      "binding_id": "d4e5f6a7-b8c9-0123-defa-345678901234",
      "event_id": "98765",
      "idempotency_key": "a3f8c2d1e4b7",
      "status": "succeeded",
      "attempt": 1,
      "http_status": 200,
      "error_code": null,
      "error_message": null,
      "duration_ms": 234,
      "completed_at": "2024-09-15T11:00:00.000Z",
      "created_at": "2024-09-15T10:59:59.000Z"
    }
  ],
  "total": 1280
}

Errors

Response

{
  "id": "e5f6a7b8-c9d0-1234-efab-456789012345",
  "binding_id": "d4e5f6a7-b8c9-0123-defa-345678901234",
  "event_id": "98765",
  "idempotency_key": "a3f8c2d1e4b7",
  "status": "succeeded",
  "attempt": 1,
  "http_status": 200,
  "error_code": null,
  "error_message": null,
  "request_body": "{"vendor":"Acme Corp","total":4950.00}",
  "response_body": "{"ok":true}",
  "duration_ms": 234,
  "completed_at": "2024-09-15T11:00:00.000Z",
  "created_at": "2024-09-15T10:59:59.000Z"
}

Errors

Response

{
  "enqueued": true,
  "idempotency_key": "a3f8c2d1e4b7"
}

Errors

Clearing the delivery log

Two write routes remove history rows. DELETE /v1/delivery/items/:id deletes one attempt record; DELETE /v1/delivery/items bulk-clears the log, honouring the same binding_id, destination_id, and status filters as the list route, so "clear only failed attempts" or "clear one binding's log" work with a single call. With no filters, every row for the organization is removed. Both routes require the write scope and an organization-scoped API key.