Webhook Delivery Evidence
Zen Mesh records delivery evidence for every webhook event, providing audit trail, tamper-evident integrity, and machine-readable verification.
What It Is
Delivery evidence is a tamper-evident record of each webhook delivery attempt. Every event that passes through the data plane generates a delivery receipt with metadata about the source, destination, delivery outcome, and cryptographic integrity proof.
Evidence Types
| Type | Description |
|---|---|
| Delivery receipts | Per-event delivery outcome with timestamps, source, destination, and status |
| Delivery history | Complete history of delivery attempts, including retries and DLQ events |
| Merkle integrity chain | Content-addressed evidence chain for tamper detection |
| Validation maps | Local validation guides for verifying evidence independently |
How It Works
- When an event is delivered, a delivery receipt is generated with the event ID, source, destination, delivery mode, timestamp, and outcome
- Receipts are appended to an audit log with hash-chain linking for tamper evidence
- Merkle integrity comparison provides drift detection across evidence snapshots
- Machine-readable manifests expose capability status and evidence references for AI and RAG systems
Related Capabilities
- Webhook Reliability — operational delivery controls
- Webhook Replay and Recovery — replay uses delivery history
- Evidence Overview — full evidence index
- Merkle Integrity — content-addressed evidence verification
Evidence and Status
Status as of 2026-06: Delivery receipts and audit logs are generated per-event. Merkle integrity chain is implemented. Machine-readable evidence manifests are published. All evidence is currently validated in local/sandbox environments.