Skip to main content
Every time Inkbox POSTs an event to one of your endpoints, it records the attempt in a delivery log. Use this log to inspect delivery status and replay supported events your endpoint missed. Payload and response content may be omitted; the log is not a substitute for authorized conversation history. Companion events expose event/scope metadata and, when known, the current message’s sender_access at its normal message location, rather than conversation content in the delivery log. Manual replay returns 409; recover from the currently authorized activation snapshot. Automatic webhook retries continue to apply. Slack diagnostics contain event coordinates instead of the original message body; Slack deliveries cannot be replayed. The log covers both subscription deliveries (message.*, text.*, imessage.*, call.ended, a2a.*, slack.*) and the separate phone.incoming_call deliveries. Subscription deliveries carry a webhook_subscription_id (call.ended rows for calls on a number you own also carry that phone_number_id); incoming-call deliveries carry only a phone_number_id and are not replayable (their response body drives live call routing, so there’s nothing meaningful to replay).

Auth


List deliveries

List logged delivery attempts visible to the caller, newest first. Returns an object with a deliveries array — not a bare array.

Query parameters

Filters AND-combine.

Response (200)

JSON

Code examples


Replay delivery

For replayable channels, re-deliver a logged event to its subscription’s current URL — and, when one is set, its current auth_token (not the token from the original attempt) — recording a new delivery row (with is_replay set to true) for the attempt. Use replayable when deciding whether to offer replay. webhook_subscription_id identifies the subscription that received the original attempt and must still be active for replay. Replay preserves the original webhook envelope’s id. Deduplicate events using that field so a replay cannot repeat an action your receiver already completed. Each replay has fresh signature headers with a new request ID and timestamp.

Path parameters

Response (200)

Returns the new replay delivery row (is_replay: true). See Delivery object.

Error responses

Code examples


Delivery object

For event webhooks, the delivery record’s event_id equals the payload envelope’s id. Use it to correlate delivery attempts with the event your endpoint received.