- Policies are insurance contracts issued to insureds
- Each policy has a number, primary insured, and effective dates
- Policies are divided into segments when exposures change mid-term
- Policies can be created directly for historical imports, or via the quote→bind flow
- Results are paginated with a fixed page size of 50
API Endpoints
- List Policies - Retrieve paginated list of policies with filtering and sorting
- Get Policy - Retrieve detailed policy information including segments, coverages, and rating inputs
- Create Policy - Create a policy directly (for historical imports)
- Delete Policy - Soft delete a policy by ID
Policy Segments
When exposures (insureds) are added, removed, or modified mid-term, policies are automatically divided into segments. Each segment represents a period where policy data is constant. Example: A policy running from Jan 1 to Dec 31 has one exposure. On June 1, a second exposure is added. The policy will have two segments:- Segment 1: Jan 1 - May 31 (one exposure)
- Segment 2: Jun 1 - Dec 31 (two exposures)
- Date range (
start,end) - Status (
bound,quoted,cancelled) - Premium and base premium totals
- Full coverage details with limits
- Exposure-level rating inputs showing how premiums were calculated
Time Travel (Historical Views)
The Get Policy endpoint supports theasOf query parameter to retrieve the policy state as it existed at a specific point in time:
- Auditing: Understanding the policy state at a specific date
- Reporting: Generating historical reports
- Debugging: Seeing how the policy looked before endorsements
Creating Policies
The Create Policy endpoint is primarily designed for historical imports where policies need to be created without going through the standard quote→bind wizard flow. Workflow:- Create insureds first via
POST /insureds - (Optional) Create broker via
POST /brokersif policy has a broker - Create the policy with insured and broker references via
POST /policies - The endpoint automatically creates insured snapshots with the provided
ratingInfo
Required Fields
Optional Fields
Policy Types
Policy Fields (List Response)
Policy Fields (Get Response)
The Get Policy endpoint returns detailed information including all list fields plus:Policy Status Values
Segment Fields
Each segment in thesegments array contains:
Exposure Fields
Each exposure in a segment contains:Rating Inputs Structure
TheratingInputs object is keyed by coverage type ID. Each coverage contains rating factor objects with:
Filtering and Sorting
Filter Parameters
Sorting Parameters
Pagination
Response includes:
items- Array of policies for the current pagetotalCount- Total number of matching policies across all pages
Permissions
Access to policies requires the appropriate permissions based on your API key:Example: Create Policy Request
201 Created
