Skip to main content
Every policy lists the lines it covers in coverages, each with a type from a fixed list. A package policy lists each line:
The type describes the coverage, not the insured’s industry. A restaurant’s liquor liability policy is liquor_liability, not “restaurant”. Sub-coverages and sublimits (business income, uninsured motorist, breach response) aren’t separate types; put them in the parent line’s description if you want them recorded.

Get the list

GET /v1/coverage-types returns every type with its definition, the common names it goes by, and any flags. It needs no scope, so any key can call it.
200 OK (abridged)

Map your line names

Your agency management system has its own names for lines of business. Build the mapping once:
  1. Call GET /v1/coverage-types and match your line names against each type’s name and aliases.
  2. Review the matches by hand, and store the mapping in your system.
  3. Map anything that doesn’t fit to other, with your line name as the description.
aliases are there to help you build that mapping. The API accepts only type values, never an alias. Send "type": "CGL" and you get a 422 with a hint:
We never guess a type for you, because the type feeds eligibility.

Flags

A flag changes how a line is treated, but never stops you quoting it:

Every type

We add types over time and never rename one. If you read a type you don’t recognize, treat it as other.