SIGNED DELIVERY
Every webhook payload is signed with a project-specific secret. Recipients verify the signature before processing.
DEVELOPERS · EVENTS
External systems
via Events.
Subscribe to signed event streams. Verified delivery, retry guarantees, and a complete audit trail for every integration — external systems receive Veritan events at their own endpoint.
EVENT MODEL
Signed. Delivered. Audited.
Veritan does not emit fire-and-forget webhooks. Every event is cryptographically signed, delivered to your registered endpoint with retry guarantees, and retained in the platform audit log. Your system can verify that a given event originated from Veritan and was not modified in transit.
RETRY GUARANTEES
Failed deliveries are retried with exponential backoff. Delivery state is visible in the Console.
AUDIT LOG
Every event: emission timestamp, delivery attempts, response codes, and final delivery state are retained.
DELIVERY ARCHITECTURE
From Veritan to your endpoint.
External systems register a destination endpoint and subscribe to event categories. Veritan emits a signed event to the registered endpoint when a matching platform event occurs. The receiving system verifies the signature and processes the payload.
EVENT DELIVERY — ILLUSTRATIVEHTTP
POST https://your-endpoint.example.com/veritan/events
Content-Type: application/json
Veritan-Signature: sha256=<hmac-signature>
Veritan-Event-Id: evt_••••••••••••
Veritan-Timestamp: 2026-08-18T00:00:00Z
{
"event": {
"id": "evt_••••••••••••",
"type": "veritan.<domain>.<event-name>",
"record_id": "<record-id>",
"state": "active",
"evidence": { "provenance": {...}, "authority": {...} },
"occurred_at": "2026-08-18T00:00:00Z"
}
}
→ 200 OK (your system acknowledges delivery)Event types follow the format veritan.<domain>.<event-name>. Actual event names are confirmed at integration time against the canonical event registry.
SUBSCRIPTION MODEL
Subscribe to the events your system needs.
Webhooks are configured per project with an explicit event category subscription list. You receive only the events your system registered for. Subscriptions are created, updated, and revoked from the Console or via the API.
ENDPOINT REGISTRATION
Register a destination URL per project. Endpoints are verified before the first delivery.
EVENT CATEGORIES
Subscribe to specific event categories: record lifecycle, evidence updates, authority changes, provenance events.
SIGNATURE VERIFICATION
Each subscription has a signing secret. Verify the Veritan-Signature header on every incoming webhook.
RETRY POLICY
Delivery is retried up to a defined limit with exponential backoff. Failed delivery is visible in the Console.
VERSIONING
Event schemas are versioned. Schema changes are announced with migration guidance before deployment.