Katexs
Webhooks and server URLs

Webhooks & events

Webhooks and server URLs

Which requests reach your servers, which stay inside Katexs, and how to receive them.

Two directions

DirectionWhat it isStatus
Katexs to your server: tool requestsWhen an agent calls a custom function, your endpoint receives a tool-calls request and answers it.Live
Katexs to your server: event notificationsCopies of call and chat events (call started, call ended with transcript, and so on) sent to an endpoint you register.Preview
Voice engine to KatexsEvery voice event is processed by Katexs for logging, billing, memory and routing. Managed for you.Live

Where tool requests go

For each custom function, Katexs sends the tool request to the first URL that is set:

  1. 1

    the function's own server URL,

  2. 2

    the agent's Server URL on the Advanced tab,

  3. 3

    otherwise Katexs handles it itself (built-in tools).

The server timeout on the Advanced tab (1 to 120 seconds, default 20) is the transport limit. Voice functions should still answer within 800 ms. See Latency and async tools.

Note

Call events that drive billing, such as the end-of-call report, always go to Katexs, whatever server URL you set. Your server URL only receives tool requests. This is what lets Katexs guarantee that every call is billed exactly once and logged under the right workspace.

Event notifications (Preview)

Event notifications will let you register an HTTPS endpoint per workspace and choose which events to receive. Each delivery will be signed, retried with backoff, and carry an event id for idempotency. The payloads follow the Event reference. To join the preview, email support@katexs.com.

Last updated November 2026 · Found a problem? Email support@katexs.com