Skip to content

Duvo Webhooks.

Duvo webhooks: the per-run webhook_url, its human request and run events, payloads, and delivery behaviour.

Duvo Webhooks

Duvo sends webhooks for one run at a time. Pass webhook_url when you start a run with POST /v2/teams/{team_id}/runs, and Duvo posts that run's events to the URL. There are no workspace-wide webhook subscriptions yet.

Events

  • human_request: the run is waiting for a person. The body carries human_request with its id, type, message, created_at and, for questions, questions. Answer it with POST /v2/runs/{run_id}/human-requests/{request_id}/respond.
  • run_completed, run_failed, run_interrupted: the run stopped. The body carries run with its status, started_at and completed_at.
  • Every body also carries event, run_id and agent_id.

Delivery

  • Each event is one POST with a JSON body (Content-Type: application/json) and a 30 second timeout.
  • Duvo does not retry a failed delivery or a non-2xx response. If an event matters, also poll GET /v2/runs/{run_id}.
  • The URL must be publicly reachable. Duvo refuses loopback, link-local and private network addresses.

Verify an event

Webhook requests are not signed yet, and there is no webhook secret. Use a URL that is hard to guess, and read the run with GET /v2/runs/{run_id} before acting on an event.

Machine-readable source:

https://www.duvo.ai/webhooks.md