Skip to main content
Webhook delivery flows through a channel-agnostic subscription resource. Each subscription names one agent identity — one HTTPS destination URL, and a non-empty subset of the event catalog. Many subscriptions can attach to the same owner; each URL receives its own POST per event, independently.
Signing keys are per agent identity. Each identity has its own key that verifies the webhooks for that identity’s mailbox, phone number, iMessage, call-lifecycle, Agent2Agent, and Slack traffic — see Signing keys.
For payload shapes, signing-key verification, and typed receiver examples, see the Webhooks guide, the Mail webhooks reference, the Phone webhooks reference, and the Slack webhooks reference. API base URL:

​
Quick start

Create an account and get your API key from the Inkbox console:

Get API key

All webhook subscription endpoints require an API key. Admin-scoped keys and human Console sessions can manage any subscription in the organization; claimed agent-scoped keys can only manage subscriptions belonging to their identity.

​
Subscriptions

Create subscription

Attach an HTTPS URL + event-type list to an agent identity, with optional delivery authenticationPOST /api/v1/webhooks/subscriptions

List subscriptions

List active subscriptions, optionally filtered by owner / URL / event typeGET /api/v1/webhooks/subscriptions

Get subscription

Fetch one subscription by IDGET /api/v1/webhooks/subscriptions/{sub_id}

Update subscription

Change the destination URL, event-type list, and/or delivery auth tokenPATCH /api/v1/webhooks/subscriptions/{sub_id}

Delete subscription

Remove a subscription — delivery stops immediatelyDELETE /api/v1/webhooks/subscriptions/{sub_id}

​
Deliveries

Webhook delivery logs show attempt status and timing. Most channels also include the signed request body and allow replay to the subscription’s current URL. Slack diagnostics contain event coordinates, not original message content, and Slack replay is unsupported.

List deliveries

List logged delivery attempts, optionally filtered by subscription / event type / successGET /api/v1/webhooks/deliveries

Replay delivery

Re-deliver a logged event to its subscription’s current URLPOST /api/v1/webhooks/deliveries/{delivery_id}/replay

​
phone.incoming_call uses separate identity configuration

The phone.incoming_call event is a synchronous control-plane callback — the response body decides whether Inkbox answers the call — so it doesn’t fan out through subscriptions. Configure it through the identity’s incoming-call action.

​
Additional resources