Skip to main content

Pending & Events

Inspect and cancel pending debounced deliveries before they fire, list the raw delivery events that drive bindings, and replay any event on demand.

Two surfaces sit underneath the delivery items and dead-letter queue: the pending (debounced) deliveries that have not fired yet, and the raw delivery events that bindings consume. Use them to see what is queued to go out, cancel a debounced delivery before it fires, and replay an event through the binding flow.

Pending deliveries are those still inside their debounce window. List them with the pending endpoint, drop a single queued job by id, or cancel all pending deliveries for one binding. Events are the upstream signals — the API's name for domain events (a case closed, a run completed) — that matched a binding; list them and replay any one to re-run its delivery.

GET/v1/delivery/pending
DELETE/v1/delivery/pending/:jobId

Path parameters

jobId*stringThe pending delivery job id.
POST/v1/delivery/bindings/:id/cancel-pending

Path parameters

id*stringThe binding id.
GET/v1/delivery/events
POST/v1/delivery/events/:id/replay

Path parameters

id*stringThe event id to replay.