Get an agent
Read one agent’s full configuration, at any version.
Authorization header reads as ‹redacted:9f2c›. Sending
that placeholder back in a later update keeps the stored secret, so reading an agent and writing it
straight back is safe.Authorizations
Your API key as a Bearer token, e.g. Authorization: Bearer vk_….
Path Parameters
The agent's id, as GET /v1/agents returns it.
Query Parameters
live, or a version number like 3. Omit for the latest version.
Response
The agent at the requested version — latest by default.
One agent at one version — the response of every agent read, create and update.
A request body is this same object minus the read-only fields, so what you send is what you read back.
The agent's id. Stable across every version.
What the agent is called. Yours to choose; never spoken to a caller.
Which version this body describes. 0-based, and the identity you use in /versions/{n} and ?version=.
This version's uuid. Pass it as agent_version_id on POST /v1/calls to pin a call to this exact version — that field takes a uuid, not a number.
True once frozen. A published version's configuration can never be edited again; branch a draft instead.
True if this is the version answering calls right now.
The highest version number this agent has.
This version's edit counter. Echo it back as If-Match on your next write and the write becomes a compare-and-set, so you cannot silently overwrite an edit made between your read and your write.
When this version was created (UTC, ISO 8601).
When this version was last edited (UTC, ISO 8601).
Which version is live, if any. null means the agent is off air and answers nothing.
Short name for this version, e.g. Shorter greeting. Editable even after publishing — it is metadata, not configuration.
Longer free text about this version.
Why this version cannot be made live, if it cannot — e.g. it pins a model that has since been retired. Empty means it can go live.
The agent's instructions. Naming a tool as <tool_name> here is what ARMS it: a tool the prompt never names is never called, and naming one the version does not have is refused on save.
What the agent says first.
The language it opens in, which others it may switch to, and what triggers a switch.
Speech recognition. GET /v1/transcribers lists valid model values.
The LLM. GET /v1/models lists valid model and provider values.
Text to speech. GET /v1/voices lists valid voice_id values, and a voice that cannot speak language.default is refused on save.
Turn-taking, interruption and noise handling — how it behaves in the back-and-forth.
Limits on the call itself: maximum duration, silence timeout, and what ends it.
Lines for inbound calls that cannot be handled normally.
The tools Vocily ships: end the call, hold, transfer, send a WhatsApp template. Each still has to be armed from the prompt.
The {{placeholders}} the prompt and tools can use. Reference them namespaced as {{custom.your_key}}, never bare.
Which knowledge bases this agent can search, from GET /v1/knowledge-bases. This list IS the attachment — there is no separate attach endpoint, and sending it replaces the whole set. An id this workspace does not hold is refused, not ignored.
Which custom-analysis groups run after each call, from GET /v1/custom-analysis. Same rule as knowledge_base_ids: the list is the attachment, and an id this workspace does not hold is refused, not ignored.
Whether the agent remembers callers between calls, and what it is allowed to remember.
Which phone and WhatsApp numbers this agent answers on. GET /v1/numbers and GET /v1/whatsapp/numbers list what you may use.
Deep link to this agent in the Vocily dashboard, for your own UI to link out to.