Overview
Enclave can deliver audit events to any HTTP endpoint in real time. Each event is signed with HMAC-SHA256, retried automatically on failure, and carries a stable JSON schema designed for long-term compatibility. Webhooks are managed at Organisation → Webhooks.Creating an endpoint
- Navigate to Organisation → Webhooks
- Click Add endpoint
- Enter the HTTPS URL of your receiver
- Choose which events to subscribe to — or select All events (
*) - Copy the generated signing secret and store it securely — it is shown once
- Click Send test event to verify connectivity
Event types
Subscribe to individual event types or use* to receive all events.
Files
Secure rooms
E-signatures
Approvals
Secrets
Security
Users
Payload format
Every delivery is an HTTP POST withContent-Type: application/json.
Fields
Ping event
When you click Send test event, Enclave delivers aping type payload:
Signature verification
Every delivery includes four HTTP headers:How the signature is computed
X-Enclave-Timestamp) concatenated with a literal . and then the raw JSON body bytes — computed before any parsing. Always read the raw body before deserialising JSON, or the byte representation may differ.
Verification examples
Framework integration examples
Read the raw body first. Parse JSON only after signature verification is complete. Some frameworks (e.g. Express with
express.json()) consume the body stream before you can read raw bytes — use express.raw() or equivalent middleware instead.Delivery and retries
Enclave considers a delivery successful when the endpoint responds with any2xx HTTP status code within 10 seconds. Any other outcome (non-2xx, timeout, connection error) schedules a retry.
After 5 failed attempts the delivery is permanently marked Failed. Failed deliveries are visible in the Delivery log tab for each endpoint so you can inspect the response body and HTTP status from each attempt.
Idempotency
Each event produces a uniqueid (the delivery UUID). If your endpoint receives the same id more than once — which can happen during retries — you can safely deduplicate by storing processed IDs.
SIEM integration
Webhooks are the recommended path for streaming Enclave events into a SIEM:- Configure a SIEM HTTP Event Collector or Data Input with an HTTPS endpoint
- Add the endpoint in Organisation → Webhooks
- Subscribe to
*(all events) or specific event categories - Use your SIEM’s built-in signature validation to verify deliveries
- Splunk HTTP Event Collector
- Elastic / OpenSearch Logstash HTTP input
- Microsoft Sentinel Logic App HTTP trigger
- Datadog Log Management
- Sumo Logic HTTP Logs source
Managing endpoints
From Organisation → Webhooks you can:- Pause an endpoint — deliveries are dropped while paused (not queued)
- Rotate the signing secret — the old secret stops working immediately; update your receiver before rotating
- View the delivery log — per-endpoint history of every delivery attempt with HTTP status, response body, and retry schedule
- Delete an endpoint — removes all future deliveries; historical delivery log is retained
Rotating a secret
- Click Rotate secret on the endpoint
- Copy the new secret
- Update your receiver to accept the new secret
- Confirm rotation