Base URL
Authentication
Include your API key on every request:
Invalid keys return
401. Valid keys without the required permission return 403.
Response format
Successful responses use this envelope:pageNo, pageSize, totalCount, and totalPages inside response.
API groups
Quick start
Create an agent with one request:botId to configure the agent, attach FAQs, and trigger calls.
Concepts
System prompts — Use Jinja2 variables such as{{ customer_name }}. Validate syntax with Validate Prompt before saving.
Multi-language agents — Up to three languages per agent. Call Get Transcriber Config and Get TTS Config before Update Agent.
Pre-call variables — Inject caller-specific fields into the prompt at call time.
FAQ knowledge base — Up to 100 Q&A pairs per agent; matched before the LLM generates an answer.
Outbound calls — Use Trigger Call with clientReferenceId to link calls to your CRM.
HTTP status codes
Best practices
- Call the Config API before creating or updating agents so ASR and TTS choices support every configured language.
- Validate prompts before saving.
- Test in development first; pass
?environment=developmentwhen required. - Log every
requestIdfor support escalations. - Keep API keys out of source control.