Home/Docs
Realtime
Webhook signature lab
Signing secrets never ship to browsers. Your integration validates delivery using the exported Node helper verifyRcLiteWebhookSignature paired with KMS-stored webhook secrets mirrored per tenant. Production workers emit X-RapidCortex-Timestamp plus comma-delimited signatures (dual-signature tolerant parsing).
Event catalog
- incident.analyzed
- risk_score.completed
- cad_export.ready
- cad_export.failed
- transcription.completed
- translation.completed
- caller_link.opened
- caller_media.uploaded
- qa_review.completed
- supervisor_flag.created
Retry-aware delivery semantics
Delivery workers SHOULD implement exponential backoff, delivery logs keyed by webhook attempt ID, hashed payload archives, replay protection with monotonic timestamps, and optional dead-letter channels for SLA breach escalations — scaffolding exists in infra tickets; see Trust Center disclosures for SLA riders.
