This documents the v1 product. It is kept for integrations already running
on it. If you are building something new, start with the
Quickstart.
workspace header.
Variants
Create an assistant
Core fields
- cURL
- Python
- Node.js
200 OK — the created assistant under data.
Variables
Declare each variable invariant.config.inputSchema, reference it in
agent.systemPrompt / agent.firstMessage as {{name}}, and supply its value
per call. Nested values use dot paths: {{customer.firstName}}.
type is one of string, number, boolean, object, array; nested shapes
use fields. A placeholder with no matching value is left in the prompt
verbatim — the assistant will read the braces aloud. Always send every
required variable.
ICP context
Shapes tone, vocabulary and pace.Call settings
slots is v1’s calling-window enforcement. Set it to your compliant window —
see India calling rules.
Analysis plan
Post-call AI evaluation. Results arrive on theend-of-call
event.
Pre-call enrichment
IfpreCall.apiPlan.url is set, we call your endpoint before the call connects
(inbound or outbound) and merge the returned data into the call’s variables, so
your {{placeholders}} can use it — greeting an inbound caller by name, for
example.
We send number and assistantId as query parameters for method: get, or as
a JSON body for method: post. Keep the endpoint fast: it sits in front of the
call.
Get an assistant
200 with the assistant under data; 404 if it is not in this workspace.
List assistants
data.
Update an assistant
There is no delete. Archive the workspace or
organization instead.
Voice gallery
slug is what goes in
agent.identity.voice — and in v2’s voice.voice_id.
200 OK
sampleAudio before you pick. Voice choice moves answer-through rates
more than prompt wording does.