Public API · v1

Build on Ondial

Server-to-server lead ingest and contact control. Create API campaigns in the dashboard, then call /api/v1 with an approved ond_live_… or ond_test_… key.

Base https://dashboard.ondial.aiAuth Authorization: Bearer …

Paths

Request key → UI campaign → push leads → status / webhooks.Ping → list Omni templates → POST /leads (call, WhatsApp, or email).List Omni templates, then POST /leads with no dial.Interactive playground — paste key, Send.reasonCode map for guards and kill switch.

Surface

Area	Methods	Notes
Core	`GET /ping`, `GET /omni/templates`, `POST /leads`	Lead upsert + list templates for WhatsApp/email
Outbound	`GET /campaigns`, `GET /campaigns/{id}`, list contacts	Read-only. Which profile/template the campaign uses
Contacts	get / calls / call detail / delete / cancel / followups	No campaign create
Events	`/events`, `/event-routes`	ERP event bus slice
Inbound agents	CRUD-ish + activate + HMS sync	Pre-owned DIDs; healthcare HMS optional

Boundaries

Via API key	Dashboard only
Push leads / follow-ups / cancel	Create & start campaigns
Event routes + events	Buy numbers & concurrency
Inbound agent on owned number (incl. HMS Custom API)	Company create, KB upload
Status poll	CRM OAuth connect
—	Credit top-up, admin

Auth (minimal)

export ONDIAL_BASE_URL="https://dashboard.ondial.ai"
export ONDIAL_API_KEY="ond_test_xxxxxxxx"

curl -sS -H "Authorization: Bearer $ONDIAL_API_KEY" \
  "$ONDIAL_BASE_URL/api/v1/ping"

Full grant flow: Request API access.