Request delivery of an existing event again

​

Requires current webhooks:manage authority and fresh application, patient consent, document disclosure and account-erasure checks. Only an originally retained recipient may replay; a new command requires an enabled, verified endpoint subscribed to the event type. Preserves the original webhook-id, occurrence and body. A new command starts up to 72 hours of retries, bounded by the original 30-day event history expiry; it never extends retention. Identical endpoint/delivery-scoped Idempotency-Key retries return current metadata even after disablement, without scheduling again or extending the deadline; current authority and retention still apply. Retired endpoints and expired or erased history are not found. A different command is refused while an endpoint delivery attempt is active. Attempts in metadata remain cumulative across retry windows. Disabled endpoints require explicit enablement before a new replay command. No payloads or signing keys are returned.

Path Parameters

Headers

Responses

  • application/json
  • application/problem+json
  • application/problem+json
  • application/problem+json
  • application/problem+json
  • application/problem+json
  • application/problem+json
  • application/problem+json
Request Example for post/v1/webhook-endpoints/{endpointId}/deliveries/{deliveryId}/replays
curl 'https://api.dev.eno.health/v1/webhook-endpoints/{endpointId}/deliveries/{deliveryId}/replays' \
  --request POST \
  --header 'Idempotency-Key: ' \
  --header 'Authorization: Bearer YOUR_SECRET_TOKEN'
{
  "id": "string",
  "eventType": "document.processed",
  "status": "pending",
  "endpointStatus": "enabled",
  "attempts": 0,
  "lastStatusCode": null,
  "acceptedAt": "2026-11-16T18:04:16.401Z",
  "nextAttemptAt": null,
  "retryDeadline": "2026-11-16T18:04:16.401Z",
  "historyExpiresAt": "2026-11-16T18:04:16.401Z"
}
Partner API reference · Check your integration’s enabled capabilities before making requests.