Overview
Configuration presets define the available coverage limit options for each coverage type. Each preset specifies a set of named limits (e.g., “Per Occurrence”, “Aggregate”) with their amounts, and can include additional settings for deductibles, defense costs, retroactive dates, and waiting periods. Presets are stored in thecoverage_limit_presets table and are scoped to a company via company_id. Each preset references a coverage type via coverageTypeKey.
Key Concepts
- coverageTypeKey: The string key of an existing coverage type (global or company-specific). Must exist in the
coverage_typestable. - limits: An object containing an array of named limit amounts and an optional
allowLimitEditsflag controlling whether users can modify amounts on quotes. - isDefault: Whether this preset is the default for its coverage type. Multiple presets per coverage type are allowed, but only one can be the default. When creating a preset with
isDefault: true, any existing default for the same coverage type is automatically set to non-default. - defenseInsideLimit: Whether defense costs count inside or outside the limit (
"inside"or"outside"). - Settings fields: Optional JSONB configuration for deductibles, limits, retroactive dates, waiting periods, and prior/pending litigation dates. These are opaque blobs passed through to the rating engine.
API Endpoints
Permissions
Request Properties
Limits Object
Response Properties (GET)
The list endpoint returns{ items, totalCount } where each item includes all request properties plus:
Nullable fields (
defenseInsideLimit, deductible, retroactiveDate, and all settings) return null when not set.