WEBHOOKS
Know what happened on a call without polling for it
Teler sends a signed message for every event on a call - so your code reacts as things happen, and can request events again through the API if a delivery is ever missed.
USE CASES
Build live call logs, alerts and data syncs on real-time call events
A live call log
Update your dashboard the moment a call starts, ends, or gets recorded. Every status change arrives as an event, so there’s no polling loop to maintain.
Automatic recording retrieval
Pull a recording into your own storage the moment it’s ready, using the time-limited URL Teler provides, no checking back to see whether it exists yet.Each recording gets its own ID (rec_<ULID>), linked to the exact call leg it came from, so reconciling recordings against call history is straightforward.
Alerting on call outcomes
Trigger a Slack message, a ticket, or an internal alert the instant a specific event, like a failed recording, comes through.
CRM or database sync
Write call events straight into whatever system your team already works in, as they happen rather than in a nightly batch.
Built for reacting to calls in real time
Signed at the source
Every message is signed with HMAC-SHA256, so verify it before acting.
Replayable if missed
It vour service misses a delivery, just request the event again via API.
Tied to the call
Every recording event carries its own ID, linked to the exact call leg.
Fires when ready
Recording events fire after the call ends, once the audio is stored.
What our customers say about us
Related Features
What kinds of events does Teler send?
Events across the call lifecycle - connection, completion, and recording, among others. See the full event list in the webhooks docs.
How do I know a webhook is really from Teler?
Every webhook Teler delivers is signed with HMAC-SHA256, using the shared secret configured on your Voice App or SIP Trunk. Verify the signature on every request - it's the only way to know the call really came from Teler.
What if my endpoint misses an event?
For recording events, you can request the recording again through the API rather than lose it.
Does recording arrive instantly?
Just after the call ends - typically within seconds, occasionally a little longer while the audio is finalized.
How long is a recording's URL valid?
You can set the expiry time yourself - the default is 15 minutes. Request a fresh one through the recording API if you need it after that.
Which AI providers work with this?
Any of them - the event model is the same regardless of what's running on your side of the call.
Build against real events,
not polling