Skip to main content

Overview

Configuration rating presets define coverage limit options stored in the rating engine revision’s config JSON (rating_engine_revisions.config.coverageLimitPresets). These endpoints are for rating-engine companies where presets live in the revision config, not in the coverage_limit_presets table. For non-rating-engine companies, use the Configuration Presets endpoints instead.

Key Concepts

  • ratingEngineRevisionId: The rating engine revision whose config contains the presets — must already exist.
  • revisionStrategy: Controls how the revision is updated — UpdateExistingRevision modifies the specified revision in place. CreateNewRevision is not yet implemented.
  • coverageTypeKey: The string key of an existing coverage type (global or company-specific). Must exist in the coverage_types table.
  • limits: An object containing an array of named limit amounts and an optional allowLimitEdits flag controlling whether users can modify amounts on quotes.
  • isDefault: Whether this preset is the default for its coverage type. When creating a preset with isDefault: true, any existing default for the same coverage type within the revision config is automatically set to non-default.
  • Settings fields: Optional JSON 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

GET Response Properties

The list endpoint returns { items }. Each item has these properties: Unlike the table-based Configuration Presets endpoint, config-JSON presets do not have createdAt, updatedAt, or retroactiveDate fields. Sorting is by setName (default) or coverageTypeKey instead of timestamps.

POST Request Properties

Limits Object