Skip to main content

Webhooks

Webhooks allow your application to receive real-time notifications about events occurring within the didlogic platform. Instead of continuously polling our API, didlogic will push data to your server via an HTTP request as soon as a specific event is triggered.

Configuration​

Currently, webhook destination URLs are managed by the didlogic technical team. To set up or modify your endpoints, please contact your Account Manager with the specific URLs you wish to use for each event type.

Available Webhooks​

Call Detail Records (CDRs)​

The system sends a JSON payload immediately after a call is terminated. This is essential for real-time billing, CRM logging, or analytics.

Payload Example:

{
  "calldate": "2026-05-12T05:17:58Z",
  "callid": "82xg86dv6jhl0p8xu0l3",
  "direction": "outbound",
  "disposition": "ANSWERED",
  "dst": "448081697031",
  "duration": 9,
  "event": "cdr",
  "src": "441273004315",
  "user_id": 76141
}

Call Recordings​

Once a call recording is transcoded and successfully stored in our S3 bucket (typically within 3 minutes post-call), a JSON notification is sent containing a pre-signed URL to the .mp3 file.

Payload Example:

{
  "calldate": "2026-05-12T05:17:58Z",
  "callid": "82xg86dv6jhl0p8xu0l3",
  "event": "recording",
  "recording_url": "https://ddl-aws-bucket.com/...",
  "user_id": 76141
}

Inbound SMS​

When an SMS is received on one of your DID numbers, didlogic relays the message data to your endpoint.

warning

Unlike CDRs and Recordings, Inbound SMS notifications are sent as a standard set of parameters (Form-encoded) rather than a JSON object. We automatically handle encoding to ensure the message text is delivered in a human-readable format.

Example Scenario: If your number +448001234567 receives a message "Hello world" from +15551234567 at 12:45 UTC on May 13, 2026, your server will receive:

"src=15551234567&dst=448001234567&message=Hello+world+&received_at=2026-05-13+12%3A45%3A40+UTC"

Security & Implementation Notes​

  • Endpoint Validation: Currently, didlogic does not provide custom headers or secret keys for request signing. We recommend ensuring your endpoint is robust enough to handle high-frequency incoming data.
  • IP Whitelisting: We do not maintain a static, public list of source IP addresses for webhooks. If your firewall configuration strictly requires an allow-list, please contact support for a list of our current IP ranges. Note that these ranges are subject to change.
  • Response Requirements: Your server should return an HTTP 200 OK status to acknowledge receipt of the webhook.