Only submitted fields are changed. The resulting agent_name, voice, business_description, and instructions must remain populated, including when a field is omitted from the request. A resulting agent_role or business_type of other requires its matching custom field to remain populated.
Submitted agent_role, business_type, and greeting values are checked against List Agent Options. The resulting voice is checked even when it was retained from the existing agent. Instructions are never regenerated on update.
Friendly agent name; required on create and must remain populated on update.
Voice key returned by List Agent Options; required on create and validated against current options after merging an update with stored details.
Role key returned by List Agent Options. Required when instructions are generated.
Required for instruction generation when agent_role is other, and on update when the resulting role is other.
Business type key returned by List Agent Options. Required when instructions are generated.
Required for instruction generation when business_type is other, and on update when the resulting business type is other.
Business name used by the agent. Required when instructions are generated.
Short business description; required on create and preview, and cannot be cleared on update.
Business contact email; must be a valid email address when provided.
Greeting style key returned by List Agent Options; defaults to friendly when omitted on create, and null clears it on update.
- Avanser Productionhttps://tapi.avanser.com/v1/aiagents/{agent_id}
- AVANSER Mock Serverhttps://avanser.redocly.app/_mock/telco-api/references/aiagents/{agent_id}
curl -i -X PUT \
-u '<username>:<password>' \
https://tapi.avanser.com/v1/aiagents/155 \
-H 'Content-Type: application/json' \
-d '{
"greeting": "warm"
}'{ "@transaction": { "id": "c9220015e2f48bc7cf4b38186a7b2025", "account-id": "1234", "request": { … } }, "response": { "message": "Success", "code": 200, "agent": { … } } }