Personal Lines Payload-Only Integration
This is the recommended launch path for personal-lines integrations. You send:- the insured profile
- current home / auto / umbrella coverage
- the quoted packages you want Nexio to compare
- inline
offeringsrepresenting the quoted line items
- ranked solutions
- per-solution scorecards
- line-level carrier breakdown
- a deterministic polling contract your team can integrate cleanly
The current production path is
POST /api/v1/jobs followed by GET /api/v1/jobs/{run_id}
polling. Webhooks are not the baseline integration path today.Integration Model
Top-Level Request Shape
What Matters Operationally
These fields drive the launch path most directly:| Field | Why it matters |
|---|---|
input.coverage_types | Creates the required lines Nexio must satisfy |
input.address.state | Drives state-based filtering |
input.vehicles or input.household.vehicles | Supports vehicle-bound filtering logic |
input.premium | Sets the submission-level premium context |
offerings[*].category | Must line up with requested coverage types (home, auto, umbrella) |
offerings[*].provider_name | Shows carrier identity in ranked output |
offerings[*].attributes.line_premium_annual | Gives integrators a clear quoted line cost |
offerings[*].attributes.package_premium_annual | Preserves package context for the quote set |
Personal Lines Input Schema
Required for a useful launch payload
Requested personal-lines coverage categories. For the current launch path this should be some
combination of
home, auto, and umbrella.Two-letter state code used by deterministic filtering.
ZIP code for the insured property / garaging context.
Driver profiles used to represent the actual quoting context.
Vehicle-level quoting information, including year, make, model, garaging ZIP, and primary driver.
Incumbent home, auto, and umbrella details. This supports comparison and review context.
The quoted packages your brokerage workflow already produced.
Strongly recommended
Named insured profile.
Home underwriting context such as square footage, construction type, renovation years, and
estimated replacement cost.
Continuous coverage, claim history, lapses, and non-renewals.
Offerings Schema
offerings is the engine-facing quoted offering set. For the payload-only launch path, this is
what Nexio actually ranks.
Inline quoted line items to evaluate. Include one offering per quoted line.
Must match the requested line, such as
home, auto, or umbrella.Carrier display name.
Quoted product or form name.
Use
quoted_line for already-quoted personal-lines offerings.The brokerage quote identifier for that line.
Annual premium for the quoted line.
Annual premium for the package the line belongs to.
Example Request
This is a shortened version of the production-tested personal-lines sample:cURL
Submission Response
Polling Response
Shortened from a real production run:What Your Team Should Build
At minimum:- Create and store a test API key.
- Submit a full request body with
inputand inlineofferings. - Persist the returned
run_id. - Poll
GET /api/v1/jobs/{run_id}untilcompletedorfailed. - Render:
- ranked solutions
- carrier / line breakdown
- line premiums
- overall score
- per-dimension scorecard
Common Failure Cases
completed with solutions_count = 0
Usually means one of these:
coverage_typesdid not line up withofferings[*].category- required lines were missing from the inline offerings set
- deterministic filtering removed all offerings for one required line
failed
Check error and error_details. Treat this as a terminal run state.
Run stays in processing
Personal-lines payload-only runs can spend meaningful time in EVALUATE while scorecards are being
computed. Poll with backoff instead of hammering the endpoint.
