Skip to content
Yuvix APIby YuvixTech
FeaturesCampaignsCRMChatbotsCall automationPricingDocs
Start freeSign in
All docs

Integrations

Call automation & telephony

Yuvix API can only see calls that pass through a telephony provider which sends call events to our webhook. It cannot detect ordinary calls to a personal mobile number or SIM, and the WhatsApp Cloud API does not report phone calls.

Option A — Twilio

  1. In Settings → Telephony, choose Twilio and enter your Account SID and Auth Token.
  2. On your Twilio number, set the Call status changes callback (StatusCallback) to the URL shown in Settings.
  3. Twilio requests are verified using the X-Twilio-Signature header.
  4. Calls ending with status no-answer, busy or canceled are recorded as missed.

Option B — Generic signed webhook

For providers such as IVR or virtual-number services, configure them (or a small relay) to POST JSON:

{
  "event_id": "unique-id-from-provider",
  "call_id": "provider-call-id",
  "event": "missed",          // incoming | missed | completed | failed
  "from": "+919876543210",
  "to": "+918012345678",
  "duration_sec": 0,
  "occurred_at": "2026-10-09T10:15:00Z"
}

Compute HMAC-SHA256 with your webhook secret over <timestamp>.<raw body> and send it as X-Yuvix-Signature: sha256=<hex>, with the same Unix-seconds value in X-Yuvix-Timestamp. Requests more than 5 minutes old are rejected, and repeated event_ids are ignored. You may also POST an array of up to 100 events.

Follow-up rules

In Calls → Follow-up rules, pick an approved template, a delay and a cooldown. Follow-ups are only sent to contacts who have opted in and haven't opted out.