OperationsCRM integration
Dialout API
How CRM-triggered outbound calls flow through Ori API and Ori Core.
Flow
Request
{
"bot_id": "bot-id-here",
"to_number": "+919999999999",
"from_number": "+911234567890",
"variables": {
"CUSTOMERNAME": "Rajesh",
"amount": "50000"
}
}Fields:
| Field | Required | Notes |
|---|---|---|
bot_id | yes | Bot to run. |
to_number | yes | Customer number. |
from_number | no | Outbound caller ID/trunk hint. |
variables | no | CRM-friendly alias for call variables. |
connected_event | no | Legacy/internal equivalent of variables. |
Do not send variables and connected_event together.
What Ori API adds
Ori API derives and forwards:
config_url = https://api.example.com/api/v1/configThis lets shared Ori Core fleet servers fetch config from the correct Ori API instance.
Common errors
| Status | Meaning |
|---|---|
| 401 / 403 | Missing or invalid API key/JWT, or an inactive/expired API key. |
| 422 | Invalid payload, or both variables and connected_event were sent. |
| 503 | No healthy Ori Core fleet capacity. |
| non-200 from fleet | Dialout failed at Ori Core/LiveKit/carrier layer. |
For API-key expiry and active/inactive behavior, see CRM API keys.