Developers
Build against the reinsurance operating record.
Request sandbox access, inspect event patterns, and define integration scope against explicit contracts and evidence semantics.
Event stream
Product proof surfaceSandbox access starts with observable events.
Developers see sample event payloads and webhook delivery states without broad production-access claims.
Webhook delivery
Sandbox event stream
Input
Event schema
source data enters the workflow
Output
Delivery log
reviewable state exits the workflow
Submission received
Source and state visibleBuild against explicit contracts.
The public page keeps examples scoped to evaluation until broader release surfaces are intended.
OpenAPI contract
Typed API shape for submissions, documents, quotes, agents, audit, and integrations with explicit maturity labels.
OpenSigned webhooks
Event delivery for workflow changes with signature verification, retry semantics, and preserved ordering.
OpenSDK generation
Generated clients are a compatibility goal; public access remains scoped to evaluation and sandbox review.
OpenSandbox access
Evaluation teams can request scoped sandbox access instead of broad public API keys or implied general availability.
OpenEvents are product evidence, not marketing decoration.
Examples use illustrative identifiers and remain evaluation-only.
{
"event": "Submission received",
"submission_id": "sub_example_1024",
"source": "example workflow",
"evidence_bundle": "repo backed",
"occurred_at": "2026-04-30T16:00:00Z"
}Request sandbox access for a ReRao evaluation.
Bring a real submission packet into a scoped design-partner evaluation for broker intake, placement handoffs, operations, or sovereign deployment.
Evaluation requested
Review-ready