Webhooks & events
Event reference
Every event in a call's life, what Katexs does with it, and which ones expect a response.
Envelope
Every event is a POST with a JSON body of the form { "message": { "type": "<event>", "call": { ... }, ... } }. The call object always carries the call id, and voice resources carry metadata.workspaceId.
Events that expect a response
| Event | Sent when | Response | Deadline |
|---|---|---|---|
assistant-request | A call arrives on a number with no agent set | { "assistantId": "..." }, a full assistant, a transfer destination, or { "error": "..." } to refuse | 7.5 s (Katexs targets 800 ms) |
tool-calls | The agent calls a tool | { "results": [{ "toolCallId", "name", "result" }] } | 800 ms for voice |
transfer-destination-request | The agent transfers and the destination must be chosen live | The destination | Short; answer immediately |
Informational events
| Event | Sent when | What Katexs does |
|---|---|---|
status-update | The call status changes: scheduled, queued, ringing, in-progress, forwarding, ended | Creates or updates the call log. Each status is processed once. |
end-of-call-report | The call has ended | Saves duration, end reason, transcript, recording, summary and analysis; charges credits once; updates the contact timeline; sends notifications; writes a trace |
transcript | Partial or final transcript lines | Not stored separately; the full transcript arrives in the end-of-call report |
speech-update | The agent or caller starts or stops speaking | Used for live monitoring |
conversation-update | The conversation history changes | Used for live monitoring |
hang | The agent has not responded for longer than expected | Useful for alerting on latency problems |
Example: end-of-call report
end-of-call-report (abridged)
{
"message": {
"type": "end-of-call-report",
"endedReason": "customer-ended-call",
"call": {
"id": "c1a4e7d0-0000-4000-8000-000000000000",
"type": "inboundPhoneCall",
"customer": { "number": "+15125550123" },
"metadata": { "workspaceId": "7f3c2a9e-0000-4000-8000-000000000000" }
},
"durationSeconds": 83,
"summary": "Caller booked a cleaning for Thursday at 2:30pm.",
"analysis": {
"summary": "Caller booked a cleaning for Thursday at 2:30pm.",
"structuredData": { "intent": "booking", "wants_callback": false },
"successEvaluation": "true"
},
"transcript": "AI: Thanks for calling Riverside Dental...\nUser: Hi, I'd like to book a cleaning...",
"recordingUrl": "https://..."
}
}Chat events
Chat conversations don't produce voice events. Their stream events are documented in the Chat streaming API, and completed conversations are written to the contact timeline.
Last updated November 2026 · Found a problem? Email support@katexs.com
