Webhook

Not yet available. This destination is on the roadmap.

The Webhook destination is the most flexible broadcast option. OpenDunes will POST a JSON payload to your endpoint for every request, letting you build any custom integration — log aggregation, alerting, internal billing, or forwarding to a destination not listed here.

What gets sent#

Each request triggers one HTTP POST to your endpoint with a JSON body:

{
  "event": "request.completed",
  "request_id": "01932c5a-...",
  "timestamp": "2026-06-23T14:05:01.123Z",
  "model": "anthropic/claude-opus-4.8",
  "messages": [{ "role": "user", "content": "..." }],
  "response": "...",
  "usage": {
    "input_tokens": 42,
    "output_tokens": 130,
    "total_tokens": 172
  },
  "cost_micro_da": 8500,
  "latency_ms": 910,
  "http_status": 200,
  "metadata": {}
}

Security#

Requests are signed with an HMAC-SHA256 signature in the X-OpenDunes-Signature header, computed over the raw request body using your webhook secret. Verify this signature before processing the payload:

import hmac, hashlib

def verify(secret: str, body: bytes, signature: str) -> bool:
    expected = hmac.new(secret.encode(), body, hashlib.sha256).hexdigest()
    return hmac.compare_digest(expected, signature)

Retries#

If your endpoint returns a non-2xx status, OpenDunes retries with exponential backoff up to three times. Events that fail all retries are dropped and logged to your dashboard.

Configuration#

Once available, configure the Webhook destination from your dashboard under Broadcast. You will need:

• URL — the HTTPS endpoint to POST events to
• Secret — used to generate the X-OpenDunes-Signature header
• Headers (optional) — additional headers to include in each request (e.g. Authorization)

Back to Broadcast overview.