Webhooks

An HTTPS URL and the event names you’d eventually want. The events list and secret are stored as given. There’s no fixed event catalog to validate against yet, so anything you send is accepted as-is.

{
  "id": "wh_f1e2d3c4b5a6",
  "url": "https://yourapp.com/webhooks/dyva",
  "events": ["message.created"],
  "secret": null,
  "created_at": "2026-03-09T12:00:00Z"
}

curl -X POST https://api.dyva.ai/v1/webhooks \
  -H "Authorization: Bearer <access_token>" \
  -H "Content-Type: application/json" \
  -d '{
    "url": "https://yourapp.com/webhooks/dyva",
    "events": ["message.created"]
  }'

There’s no update endpoint today. To change a URL or event list, remove the old registration and create a new one.

[
  {
    "id": "wh_f1e2d3c4b5a6",
    "url": "https://yourapp.com/webhooks/dyva",
    "events": ["message.created"],
    "secret": null,
    "created_at": "2026-03-09T12:00:00Z"
  }
]

HTTP/1.1 204 No Content

curl -X DELETE https://api.dyva.ai/v1/webhooks/wh_f1e2d3c4b5a6 \
  -H "Authorization: Bearer <access_token>"

If you need real-time updates today

Poll instead. It’s less elegant, but it’s the mechanism that’s actually live. See Rate Limits for how often you can reasonably check.

# Check for new messages in a conversation on a timer
curl https://api.dyva.ai/v1/conversations/conv_j1k2l3m4n5o6/messages \
  -H "Authorization: Bearer <access_token>"