Update Ai Agent
Update an existing AI agent's configuration, tools, or knowledge bases. Use deploy=true to apply changes immediately.
Request
- Base URLhttps://api.xpander.ai (the document declares no server; this is the origin it was published from)
- AuthAPI key in header x-api-key
Path parameters
Query parameters
Automatically deploy the agent after updating to apply changes immediately. Without this, changes are staged but not active until a PUT deploy call.
Request body
Fallback organization user for unattended executions; also used for user budgets and usage attribution.
Set automatically by the API service from the authenticated request.
Set automatically by the API service from the URL path parameter.
Human-readable name for the agent.
A brief description of what the agent does.
Emoji icon displayed next to the agent name.
Avatar identifier for the agent's visual representation.
Enumeration of the agent types.
Attributes: Manager: marks the agent as a Managing agent. Regular: marks the agent as a regular agent. A2A: marks the agent as an external agent used via A2A protocol. Curl: marks the agent as an external agent used via a CURL. Orchestration: marks the agent as an Orchestration object.
Enumeration of possible agent statuses.
Attributes: DRAFT: Agent is in a draft state. ACTIVE: Agent is active and operational. INACTIVE: Agent is inactive and not operational.
The specific model identifier.
Custom API base URL for the LLM provider.
Reference key to stored LLM API credentials.
Additional HTTP headers for LLM requests.
Description of expected output format.
JSON Schema for structured output.
Execution framework.
Enable deep planning mode.
Force deep planning for all tasks.
Target deployment environment.
Voice ID for TTS output.
Enable NeMo guardrails.
Enable supervised mode.
Run the agent in autonomous mode.
Omni's entry on the agent's caller list: Omni finds the agent and can send it tasks. Changing it is for the agent owner or an organization admin.
Run the SDK automatic context optimizer.
Allow invocation from the developer API and webhooks.
Stage edits as a draft before publishing. Ignored for agents while drafts are off (the default): every edit saves to live.
Approval-required workspace commands: a list of {match, unless?, note?, approvers?, channels?}. match is the LITERAL command text (a plain substring, no regex, no escaping); unless names a safe variant that stays exempt (e.g. '--dry-run'). A workspace command containing a match is held for a person's approval before it runs - even on an autonomous/scheduled run. approvers ({user_ids, group_ids}) names who is asked; omit it and the agent's owner is asked. channels (e.g. ['slack']) routes the notification; omit it and each approver's own preferences decide.
Allow the agent to schedule its own future runs.
Allow the agent to archive and restore its own conversations.
Per-task lifetime cap on chained self-schedules.
Enable event streaming.
Enable OIDC pre-authentication.
Allowed OIDC audiences.
Forward OIDC token to LLM.
OIDC audience for LLM access.
OIDC audience for MCP access.
Response
Successful Response
A platform-made agent: the gateway one is hidden from lists, counts and delegation; every kind stays out of the agents quota.
Enumeration of possible agent statuses.
Attributes: DRAFT: Agent is in a draft state. ACTIVE: Agent is active and operational. INACTIVE: Agent is inactive and not operational.
Organization user to run as when a non-UI invocation has no resolved user.
Enumeration of the agent types.
Attributes: Manager: marks the agent as a Managing agent. Regular: marks the agent as a regular agent. A2A: marks the agent as an external agent used via A2A protocol. Curl: marks the agent as an external agent used via a CURL. Orchestration: marks the agent as an Orchestration object.
Changes
No recorded changes to this operation across all 4 revisions of this API.