Skip to main content

Shipped surface

Scoped access

Default API keys include lead/inbound/calls:read/credits:read/webhooks:write. Super Admin may also grant:
  • companies:* / knowledge:* - company profiles + KB metadata
  • analytics:read - call aggregates
  • recordings:read - short-TTL signed recording URLs
Missing scope → 403 with reasonCode: "forbidden" and a missing array. Company and KB responses never include SMTP passwords, WhatsApp tokens, or file download URLs. Call list/detail never return permanent recording storage URLs.

Explicitly not in public API

Custom CRM pattern

  1. UI: empty API campaign → start
  2. API: POST /leads (or POST /events with a mapped eventType)
  3. WhatsApp/email: GET /omni/templates then pass ids + templateVariables / whatsappParams - guide
  4. Optional: POST /api/v1/webhooks (or API Access → Notifications) for status / billing callbacks
  5. Usage UI: poll GET /calls + GET /credits/transactions; see Healthcare HMS integration
  6. Inbound: wire Sheets/Zoho/Custom API in UI → POST .../crm/lookup when you need a read without a live call.

Versioning

/api/v1 remains supported ≥ 12 months after any future /api/v2 GA; breaking changes get ≥ 90 days notice.