Dhvanee DocsDashboard
Public API

Webhooks

Outbound HTTPS deliveries for contact and call events, signed with HMAC-SHA256.

Create subscriptions in the dashboard under Settings → Developer Access (session auth). Data API keys cannot create webhook subscriptions.

The machine-readable contract is `openapi.public.yaml`. Download it for clients and codegen. This site has no live Try-it console.

Events

  • Contact: created, field_change, merged, imported, sync, note, consent, task
  • Call: call_started, call_ended, call_analyzed — call_id matches POST /v1/calls

Headers on each delivery

HeaderMeaning
X-Dhvanee-EventEvent name
X-Dhvanee-DeliveryDelivery id
X-Dhvanee-TimestampUnix timestamp used in the signature
X-Dhvanee-Signaturesha256= + HMAC-SHA256 of timestamp + "." + body

Example delivery your endpoint receives

curl -sS -X POST "https://example.com/dhvanee-events" \
  -H "Content-Type: application/json" \
  -H "X-Dhvanee-Event: call_ended" \
  -H "X-Dhvanee-Delivery: 9f3c0d2e-…" \
  -H "X-Dhvanee-Timestamp: 1730000000" \
  -H "X-Dhvanee-Signature: sha256=…" \
  -d '{"id":"…","type":"call_ended","call_id":"…","data":{"call":{"status":"completed"}}}'

Verify a delivery

python - <<'PY'
import hmac, hashlib
secret, ts, body = b'whsec_…', b'1730000000', b'{"type":"call_ended"}'
sig = 'sha256=' + hmac.new(secret, ts + b'.' + body, hashlib.sha256).hexdigest()
print(sig)
PY
The signing secret is shown once when you create the subscription. Store it like an API key.

Harden your endpoint

  • Reject the request when abs(now_unix - X-Dhvanee-Timestamp) > 300 seconds
  • Verify X-Dhvanee-Signature on the raw request body bytes
  • Treat each X-Dhvanee-Delivery id as single-use (store seen ids at least 24 hours)
Was this page helpful?
Webhooks · Dhvanee Docs