Webhooks overview

Webhooks are how Drömlik pushes real-time events to your application. You configure one or more URLs in the admin console, pick which event types you care about, and Drömlik sends an HTTPS POST whenever those events happen.

When to use webhooks vs WebSocket

• Webhook — your application has a public HTTPS endpoint. Best for serverless workloads, Zapier-style automations, and integrations that don't need a persistent connection.
• WebSocket — your application keeps a long-lived connection open. Lower latency, better for live dashboards and CTI screen-pops.

Available events

The full event catalogue is in Zapier triggers (the same set is available via webhook). Some highlights:

• 30011 — call state changed
• 30009 — extension presence changed
• 30031 — inbound SMS
• 30015 — voicemail received
• 30007 — trunk status changed

Payload format

POST https://your-app.example.com/webhook
Content-Type: application/json
X-Dromlik-Signature: sha256=<hex>

{
  "event": 30011,
  "timestamp": 1717250400,
  "tenant": "acme",
  "data": {
    "call_id": "c_abc123",
    "from": "+46812345678",
    "to": "101",
    "state": "ringing"
  }
}

Security

Every request is signed with HMAC-SHA256. Verify the X-Dromlik-Signature header before processing the payload — see Configure webhooks.

Delivery guarantees

• At-least-once. A retry happens if your endpoint returns a non-2xx response or times out (10 seconds).
• Retries. Exponential backoff for up to 24 hours.
• Idempotency. Every event carries a unique event_id; deduplicate on it.