Create agent (template-driven)
Creates a new agent for the campaign using server-managed voice and agent-type templates. Unlike POST /agent/{campaignId}, this endpoint resolves voice settings and scripts from template IDs rather than requiring inline configuration.
Required fields:
Name— display name for the agent (always required).VoiceId— ID of the voice template (always required; defines TTS provider, language, and voice settings).
agentTypeId — ID of the agent-type template (defines scripts and conversational behavior) — is optional. When it is omitted, AgentTypeName, PreScript, and PostScript become required instead.
On success returns 200 with { campaignId, assistantId }.
Available VoiceId values
Pick the ID column value for the voice you want. These are Atlas catalog IDs — they are not the underlying provider’s voice IDs, and the two are interchangeable only by coincidence. A voice that speaks more than one language per call has its own entry under Multilanguage with a different ID from its single-language entry.
English (US)
English (UK)
English (Australia)
Spanish (es-US)
French (fr-FR)
Romanian (ro-RO)
German (de)
Hindi (hi-IN)
Hebrew (he-IL)
Turkish (tr-TR)
Multilanguage
Use these when the agent must speak multiple languages in one call.
Available agentTypeId values
The chosen agent type must match both the language and the campaign type of the campaign referenced by campaignId. Otherwise the request fails with a validation error.
Campaign types are: inbound, outbound, web, messages.
Inbound
Outbound
Web
Messages
Authentication
Your Atlas API key. Get it from the Atlas Portal under Settings > API Keys.
Path parameters
Request
Agent-type template ID. When provided, scripts and settings are resolved from the template. When omitted, AgentTypeName, PreScript, and PostScript are required.
