Voice webhooks
Call events and tool requests from the voice provider during a phone call with an agent, how they are verified, and their limits.
When an agent takes phone calls, the voice provider (Speko) talks to Veyra through two webhooks during each call:
POST https://intelligence-api.veyra.so/api/voice-webhooks/{publicId}/events
POST https://intelligence-api.veyra.so/api/voice-webhooks/{publicId}/tools- events report the call's lifecycle: started, answered, ended.
- tools carry requests the voice session makes to the agent's tools during the call.
Verification
Each callback is verified on its original bytes with the provider's signature and a per-session capability. Nothing bypasses this check, not even a signed-in person.
Responses and limits
| Status | Meaning |
|---|---|
200 |
Handled; the JSON body is the answer for the provider. |
400 |
The callback is malformed. |
401 |
The signature is invalid. |
403 |
Voice connections are turned off. |
413 |
The callback body is too large. |
429 |
More than 600 callbacks per minute from one address. |
Responses are never cached (Cache-Control: no-store).
Calls and tasks
A call is linked to a task, so its transcript and outcome stay with the work. Callers who are not verified members can only reach the restricted guest intake you configured; private work needs an authenticated caller.
Voice setup is managed from the console. The endpoints behind it work only in a signed-in console session, so they are not part of the key-based API reference.