Agents API
Update Agent
Update an existing agent’s configuration — all fields are optional
PUT
Overview
Update an existing voice agent’s configuration. All request body fields are optional — only the fields you include are modified. Unspecified fields retain their current values. This endpoint is the primary way to configure an agent’s ASR, LLM, TTS, language settings, advance settings, and integrations.Required Permission
agents
Path Parameters
Top-Level Request Body Fields
advanceSettings Fields
ASR Model Compatibility — advanceSettings Reference
Each advanceSettings field is valid only for specific ASR model types. Sending an incompatible field returns HTTP 400.
Example cURL
Update Messages
Full Configuration Update
Response
Success (200)
Error Responses
400 Bad Request - Validation errorConfiguring a Multilingual Agent
SetbotDetails.language to an array of up to three language codes. The selected ASR model must support every language in the list — use Get Transcriber Config with multiple language parameters to identify compatible options. The TTS voice must also support all configured languages — use Get TTS Config similarly. LLM models are language-agnostic.
Use Cases
- Updating agent messages for seasonal campaigns or new use cases
- Fine-tuning the system prompt based on observed performance
- Switching ASR, LLM, or TTS providers and models
- Enabling advanced features like voicemail detection or call transfer
- Configuring a post-call webhook for CRM updates or analytics pipelines
Save the
requestId from every response. You will need it if you contact Inya support to trace a specific request.Authorizations
API key with 'agents' permission
Path Parameters
Unique identifier of the agent
Body
application/json
Supports Jinja2 template variables, e.g. {{ customer_name }}
Available options:
implicit, explicit Required range:
x >= 1