Skip to main content

Delivery

Once you've subscribed, this page is how events actually reach you: what the request we send to your URL looks like, and the three things delivery does not promise — no retries, no proof it came from us, and no guaranteed order. Knowing these up front is what keeps a receiver from losing events or trusting the wrong request.

The request we send​

POST /your/endpoint HTTP/1.1
Content-Type: application/json

{ … the event body … }

Every event is delivered as a single HTTP request like the one above. Here is what to expect from each part of it:

DetailWhat to expect
MethodPOST, always
Content-Typeapplication/json
Timeout30 seconds total — from first contact to your reply
RetriesNone
Signature (proof it's from us)None — see Verifying
OrderNot guaranteed — events can arrive out of order
RedirectsFollowed — if your URL redirects elsewhere, we follow it
Encryptionhttps recommended; plain http is accepted

We ignore whatever your endpoint sends back — just reply quickly to confirm you received it.

No retry​

danger

If your endpoint is down, unreachable, or slower than 30 seconds when an event fires, the event is lost permanently. There is no retry, no stored copy, and no way to ask for it again.

Backfill from the REST API for anything you cannot lose:

EventBackfill with
AccountSMSSMS history
AccountEndedCalls, UserEndedCallsCall history / reports
AccountAITranscriptionTranscription reports
AccountRealTimeCallsNothing. Live state is not recoverable after the fact.

Out-of-order events and duplicates​

A …RealTimeCalls event can arrive after the …EndedCalls event for the same call, so order events by the timestamps inside the payload, not by the order they arrive.

There's no delivery id to spot repeats with, so make your own key from the event's contents — callId + status for calls, id for SMS — and skip any you've already handled.

Testing a receiver​

There is no test-event button and no sandbox generator. Point a subscription at a capture service (webhook.site, ngrok to your laptop), then trigger the event for real — send yourself a text, make a call — and read what arrives.