Skip to main content
DialNexa sends webhook events to your endpoint using HTTP POST.

Quick start

  1. Register a webhook URL in the dashboard.
  2. Save your webhook secret securely.
  3. Verify every incoming signature before processing events.
  4. Parse event_type and handle the event-specific payload.

Request format

Every webhook request has this high-level structure:
  • event_type: The event name used for routing.
  • payload: Event-specific data.

Supported event types

call_initiated

Sent when a call starts.

call_ended with status: "hangup"

Sent when a call ends without completing. Common disconnection_reason values:
  • user_did_not_pick_up: The recipient did not answer.
  • user_busy: The line was busy.
  • invalid_phone_number: The dialed number is not valid.
  • network_failure: A network-level error occurred.
  • unknown: The reason could not be determined.

call_ended with status: "completed"

Sent when a call completes. This payload can include transcript, summary, recording URL, and post-call analysis fields.
recording_url values are pre-signed links and expire after 7 days.

transfer_completed

For conversational agents using a Transfer node, this event is emitted when handoff is processed.

call_ended (transferred calls)

Completed transferred calls can include an additional call_transfer object for transfer metadata.

Signature verification

Every webhook POST includes an x-dialnexa-signature header. DialNexa computes this value as an HMAC-SHA256 hex digest over the entire request body (the raw JSON bytes sent in the POST) using your webhook secret as the key.
Sign and verify the full request body exactly as received. Do not hash only the inner payload object, and do not re-serialize a parsed JSON object unless you can guarantee byte-for-byte parity with what DialNexa sent.

Verification checklist

  1. Read the x-dialnexa-signature header.
  2. Read the raw request body as bytes (before JSON parsing).
  3. Compute HMAC_SHA256(raw_request_body, WEBHOOK_SECRET).
  4. Compare expected vs received signatures using a constant-time comparison.
  5. Reject on mismatch, then parse JSON and handle event_type and payload.

Node.js example

Python example

Secret rotation

Rotating your webhook secret updates all webhooks in your organization immediately. The old secret is deactivated and the new secret takes effect right away.
  • Update your webhook server configuration to use the new secret before or immediately after rotation.
  • Keep deployment steps ready to avoid signature mismatches during rollout.
  • Validate signature checks in staging before rotating in production.

Register Webhook

All webhook configuration is managed through the DialNexa dashboard, no API calls required.