Create a new agent
You can create a new agent by passing the name of the agent in the request body. You can use update-workflow endpoint next to assign custom workflow to the agent.
Request body
Ambient background sound during calls. Options: '' (none), 'office', 'cafe', 'call_center', 'static'. Note: this value is currently overridden by the server default on creation; update via PATCH after creation.
The global knowledge base ID of the agent. You can create a global knowledge base by using the /knowledgebase endpoint and assign it to the agent. The agent will use this knowledge base for its responses.
The LLM model to use for the agent. Note: gpt-5.2, electron-kogta, and electron-kogta-v2 require org-level access and return 403 if not enabled. workflowType must be single_prompt to use gpt-realtime or gpt-realtime-mini.
The default variables to use for the agent. These variables will be used if no variables are provided when initiating a conversation with the agent.
Set global instructions for your agent's personality, role, and behavior throughout conversations. Note: Only used for workflow_graph agents. Maximum 4000 characters.
IDs of telephony products (phone numbers) to associate with the agent for inbound/outbound calls.
The type of workflow configuration. workflow_graph uses a node-based visual workflow, single_prompt uses a simple prompt-based configuration.
The first message the agent sends when a conversation starts.
When true, the user's audio is muted until the agent has finished its first response.
Whether the user can interrupt the agent while it is speaking.
When true, the agent waits for the user to speak before sending the first message.
Seconds the agent waits after being interrupted before resuming speech.
Configuration string for call disposition tracking.
Whether the agent accepts inbound calls.
Whether style guide enforcement is applied to agent responses.
Whether speech formatting is applied to the agent's responses.
Response
Agent created successfully
The ID of the created agent
Example response
{
"status": true,
"data": "60d0fe4f5311236168a109ca"
}