Webhooks and delivery

Create and manage subscriptions through the deployed /v1/webhooks operations in the API reference. Use the required scopes and tenant credentials advertised by capabilities. Subscription endpoints are subject to outbound and destination policy; registration does not prove receiver availability.

For durable agent terminal events, use the version-2 completion and delivery contract: preserve event identity, verify the raw signed body before parsing, acknowledge durably and deduplicate before any business side effect. Transport acknowledgement is separate from business completion. Replaying a delivery must not create a new run or a duplicate effect.

Use the tested integration recipes for a persistent webhook inbox and verified artifact workflow. Legacy delivery and version-2 durable delivery have different guarantees; inspect the event version and subscription's documented contract. Diagnostics with no delivery rows are not proof of successful delivery.

The older unqualified event catalogue and hand-maintained payload examples are preserved as historical material. Current schemas, signatures, retries and evidence requirements come from the deployed reference and completion contract.