Webhook

documentLifecycle

​

A committed owner event is delivered to each subscribed, verified endpoint. Delivery is at least once with no ordering guarantee. The event id and body remain stable across retries; webhook-timestamp identifies the current attempt. Automatic retries stop within 72 hours of first durable acceptance. Event and delivery history expires after 30 days; current authority is required before each disclosure. Processing completion is separate from clinical publication and patient-record availability. document.downloaded means controlled server retrieval/decryption and durable audit acceptance before byte handoff, without proving remote consumption. Signatures use Standard Webhooks HMAC-SHA256 over webhook-id + '.' + webhook-timestamp + '.' + the exact request bytes.

Headers

Body·

required
application/json

Responses

  • Acknowledged; any 2xx response acknowledges delivery

Request Example for postdocumentLifecycle
{
  "id": "",
  "type": "document.processed",
  "timestamp": "2026-11-16T18:04:16.498Z",
  "data": {
    "status": "processed"
  }
}
No Body
Partner API reference · Check your integration’s enabled capabilities before making requests.