Webhooks

Signed events with visible delivery state

Implementation detail for the event catalog: verify every signature, return a successful response promptly, and use delivery logs when a consumer falls behind. The supported event names live on the events overview.

Supported events

  • call.started
  • sms.received
  • sms.sent
  • sms.failed
  • contact.changed
  • presence.changed

Delivery lifecycle

  1. 01

    Create an HTTPS endpoint and select supported events

  2. 02

    Verify the signed body before processing

  3. 03

    A failed attempt retries with backoff

  4. 04

    Inspect dead state and replay after the consumer recovers

Operational boundary: Retries improve delivery reliability but do not replace an idempotent event consumer.

Integration Hub webhook controls
Real endpoint and delivery controls · synthetic data · secret fields redacted

Implement signature verification

Integration planning

Plan the events your systems should receive.

Let’s find the right way to connect your business.