Webhooks

Webhooks are planned notifications about durable operations. They do not transfer ownership, authorize new work or replace result retrieval.

Design a receiving boundary

A future customer receiver will need a published signature scheme, raw-body verification, timestamp/replay checks and an event identity for deduplication. Do not invent the signature header or secret format before the contract is released.

Acknowledge receipt after you have safely recorded the event for your application. Handle duplicate and out-of-order delivery without recreating the underlying operation.

Retrieve the result

Use the authorized result reference when available. A delivery timeout does not mean the work failed, and a callback's arrival does not prove every downstream consumer is current.

Keep customer notifications separate from private provider callbacks. Provider ingress and internal event-bus subjects are not general customer subscription topics.

Protect endpoint configuration

Only an authorized administrator should change a receiver or its secret. URL validation must prevent internal-network access and unsafe redirects. Never include credentials or private evidence in a callback URL.

Availability

No webhook subscription or live delivery is enabled by these developer keys in this release. The page reserves the integration contract; it does not provide a test-send control or an executable event schema.