Webhooks
How Dialgem notifies your servers about calls, which events exist, and where to find setup, verification and retry details.
Dialgem sends a signed POST to your server when something happens on a call. You choose where, and for which events, with webhook endpoints. A webhook you set on a single agent keeps working alongside them.
Use webhooks to save a finished call and its transcript to your own database, update a CRM when a call ends, trigger a follow-up when the analysis is ready, or react to a transfer.
How it works
Something happens on a call
A call connects, finishes, is analysed, or is transferred.
Dialgem sends a signed request
A POST with a JSON body goes to every endpoint subscribed to that event. It carries a signature made with that endpoint's secret.
Your server checks it and answers 2xx
Verify the signature, store the event, and reply quickly. Do the slow work afterwards.
If you do not answer, Dialgem retries
A failed delivery is retried for about 19 hours, with growing gaps.
Events
| Event | When |
|---|---|
call_started | A call connects. |
call_ended | A call finishes. The body has the transcript, cost and disconnection reason. |
call_analyzed | The post-call analysis (summary, sentiment, your custom fields) is ready. |
transcript_updated | After every turn while the call is live. High volume. |
transfer_started, transfer_bridged, transfer_cancelled, transfer_ended | Around a transfer. |
campaign_started, campaign_paused, campaign_resumed, campaign_completed, campaign_cancelled | A campaign changes state. Endpoints only. The body has campaign instead of call. |
Every call event body is { "event", "call_id", "agent_id", "call": { ... } } with the full call record under call, so a receiver that only routes on ids never has to open it. The event reference lists every field.
Guides
Add a URL, choose events, store the secret, send a test, and write a receiver.
Check that a request really came from Dialgem, with the SDK or by hand, and rotate secrets without downtime.
The retry schedule, what to build against, and how to inspect and resend deliveries.
Every event and every field of the call record.