Overview
Place a conversation workflow call request to initiate interactive voice conversations.- Send a conversation workflow request and receive a batch ID
- Use the batch ID to track the processing status of your conversation requests
- The workflow must be of type “CONVERSATION” and have “ACTIVE” status
Authentication
All API requests require an API key to be included in the headers:Endpoint
Request Body JSON
| Field | Type | Description | Required | Options | Default |
|---|---|---|---|---|---|
workflow_id | String | Unique identifier for the conversation workflow to be executed | yes | ||
workflow_params | Array | Array of objects containing phone numbers and workflow variables. Phone number is required for each entry. | yes | ||
tts_voice_accent | String | Accent for the voice used on the call | no | pidgin, english | pidgin |
tts_voice_gender | String | Gender of the voice used on the call | no | male | female | female |
Basic request and response sample
Workflow Message Requirements
- The workflow must be of type “CONVERSATION” and have “ACTIVE” status
- Use double curly braces
{{parameter_name}}syntax to insert dynamic values in your message template - Example: “Hello
{{name}}, your appointment is scheduled for{{date}}at{{time}}” - The endpoint creates a batch record for processing multiple conversation requests
Quotas and Limits
- Rate limit: 5 requests per second
- Workflow must be of type “CONVERSATION” (not “ROBOCALL”)
- Workflow status must be “ACTIVE”
