Webhooks

Phone Text Event

Fired for text-message lifecycle events on a phone number with an active text-event subscription. Covers inbound delivery (text.received) and outbound delivery state transitions (text.sent, text.delivered, text.delivery_failed, text.delivery_unconfirmed). The request body uses the standard {event_type, timestamp, data} envelope with data.text_message, data.contacts, and data.agent_identities (both lists, possibly empty). This is fire-and-forget: the response status is logged but does not affect text processing.

If your organization has a signing key, every webhook includes three headers:

  • X-Inkbox-Request-ID — UUID for deduplication.
  • X-Inkbox-Timestamp — Unix timestamp in seconds.
  • X-Inkbox-Signaturesha256={HMAC-SHA256 hex digest} over {request_id}.{timestamp}.{raw_body}.
postWebhook/phone-text

Payload

idstring required

Stable per-event id (evt_...); idempotency key, stable across replays.

event_type'text.received' | 'text.sent' | 'text.delivered' | 'text.delivery_failed' | 'text.delivery_unconfirmed' required
timestampstring date-time required

ISO 8601 timestamp of when the event occurred.

Response

Successful Response

{"stackTrail":"webhooks:/phone-text:post:responses:200:content:application/json:schema","oasType":"schema","type":"unknown"}

Changes