Integration Guide

PolicyOne participates in the OnePolicy platform event bus as both a publisher and subscriber.

  • Publishes events:policy — policy.bound, policy.issued, policy.cancelled, policy.renewed. BillingOne is the primary consumer.
  • Consumes events:claims — claim.settled from ClaimsOne to keep underwriting data current in real time.

Available Integrations

IntegrationStreamDirectionEventsStatus
BillingOne — Bind & Issuanceevents:policyPolicyOne → BillingOnepolicy.bound, policy.issued✅ Live
ClaimsOne — Claims Eventsevents:claimsClaimsOne → PolicyOneclaim.settled✅ Live
BillingOne — Payment Eventsevents:paymentBillingOne → PolicyOnepayment.charged, payment.failedPlanned
ISO ClaimSearchExternal APIClaimsOne → PolicyOneCLUE lookupsVia ClaimsOne

BillingOne Integration

When an agent binds a quote, PolicyOne writes a policy.bound event to the outbox atomically, then OutboxPublisher streams it to Redis where BillingOne's PolicyEventsConsumer creates the billing account.

Rendering diagram…

See the BillingOne Integration section for full details.


Claims Integration

When a claim settles in ClaimsOne, PolicyOne's ClaimsEventsConsumer reacts in real time:

Rendering diagram…

See the Claims Integration section for full details.


Section Contents

BillingOne

PageWhat you'll learn
① OverviewOutbox pattern, design decisions, component index
② ArchitectureC4 L1–L3 diagrams, DB tables, Redis stream layout
③ Event FlowSequence diagrams — happy path, retry, DLQ
④ Payload ReferenceEvery field in PolicyBoundPayload and PolicyIssuedPayload
⑤ OperationsEnv vars, monitoring, troubleshooting, local dev

ClaimsOne

PageWhat you'll learn
① Claims IntegrationPurpose, stream map, consumer group details
② ArchitectureC4 context and container diagrams
③ Event FlowSequence diagrams — receive, process, agent task creation
④ Large Loss WorkflowWhat happens after policy.agent_tasks is created
⑤ OperationsEnv vars, monitoring, DLQ management