Push leads from your CRM

Before you POST: Lead setup with your campaignId — copy call.lead / email.lead / whatsapp.lead. Optional Validate lead (nothing is created).

Direct lead push

curl -sS -X POST "$ONDIAL_BASE_URL/api/v1/leads" \
  -H "Authorization: Bearer $ONDIAL_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: crm-$(date +%s)" \
  -d '{
    "campaignId": "YOUR_CAMPAIGN_ID",
    "phone": "+919876543210",
    "name": "Asha",
    "channel": "call",
    "consent": {
      "outboundCall": true,
      "capturedAt": "2026-08-11T10:00:00Z",
      "source": "crm"
    },
    "metadata": { "leadId": "CRM-99" }
  }'

ERP-style events

Map eventType → campaign via Settings or POST /api/v1/event-routes
POST /api/v1/events with eventType + phone (+ consent)

Full walkthrough (list templates → fill params → send): Send WhatsApp and email.

Direct WhatsApp + email (no dial)

Templates are resolved automatically: request ids → campaign Follow-up pick → Omni default verified profile + attached template. You do not need to turn campaign Follow-up on if Omni already has the profile and template.

curl -sS -X POST "$ONDIAL_BASE_URL/api/v1/leads" \
  -H "Authorization: Bearer $ONDIAL_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "campaignId": "YOUR_CAMPAIGN_ID",
    "phone": "+919876543210",
    "email": "asha@example.com",
    "name": "Asha",
    "channels": ["whatsapp", "email"],
    "whatsappScheduledAt": "2026-08-13T06:00:00Z",
    "emailScheduledAt": "2026-08-13T06:30:00Z"
  }'

Clock	Template sent
`whatsappScheduledAt`	Resolved WhatsApp template (`whatsappTemplateId` in the response)
`emailScheduledAt`	Resolved email template (`emailTemplateId` in the response)

Optional overrides: whatsappTemplateId, whatsappProfileId, emailTemplateId, emailProfileId from GET /api/v1/omni/templates. Pass merge fields with the lead:

{
  "templateVariables": { "contact_name": "Asha", "city": "Ahmedabad" },
  "whatsappParams": ["Asha", "CRM-99"]
}

Omit the clocks to send as soon as Calling_system1 picks up the queue. Poll GET /api/v1/contacts/{id} for whatsappQueueStatus / emailStatus and the pending template ids.

Register then follow-up

POST /leads with "channel": "none"
POST /api/v1/contacts/{id}/followups

Status + conversation back to CRM

Save contactId from POST /leads
Poll GET /api/v1/contacts/{id} (see lastCall) or listen for call.status webhooks
GET /api/v1/contacts/{id}/calls — dial list (hasAnalysis, optional summary)
GET /api/v1/contacts/{id}/calls/{callId} — transcript/turns + normalized analysis (no internal blobs)

Analysis can lag call completion — poll until hasAnalysis: true. Optional: register HTTPS webhooks in API Access → Notifications (X-Ondial-Signature).

Start

Build

Concepts

Ops

Push leads from your CRM

Direct lead push

ERP-style events

Direct WhatsApp + email (no dial)

Register then follow-up

Status + conversation back to CRM

​Direct lead push

​ERP-style events

​Direct WhatsApp + email (no dial)

​Register then follow-up

​Status + conversation back to CRM

Direct lead push

ERP-style events

Direct WhatsApp + email (no dial)

Register then follow-up

Status + conversation back to CRM