Jurisdictions

Jurisdictions represent areas governed by distinct government entities, such as U.S. states. Insurance product details may vary by jurisdiction based on government regulations or market characteristics.

To support this differentiation, quotes, policies, and resources can be associated with jurisdictions.

Resource Selection

Jurisdictions affect resource selection logic. The system executes the following logic when selecting resources:

Given a quote or policy, and the staticName of a resource, for each resource group with a selectionStartTime equal to or earlier than the current time:

The system will identify the resource instance associated with the jurisdiction that matches the jurisdiction associated with the quote or policy, if it exists in the resource group, and add it to a temporary list.

If no such resource instance exists in the resource group, the system will identify the resource instance that is not associated with any jurisdiction, if it exists in the resource group, and add it to the temporary list.

The system will then select the resource instance with the most recent selectionStartTime from the temporary list.

The Resource Selector, Document Selection Plugin, and the default document selection flow all execute the resource selection logic described above.

Note

Jurisdictions will be incorporated into future features, including producer management and tax management.

Configuration

Jurisdictions must be defined in the jurisdictions configuration object before they can be associated with quotes, policies, or resources. Each jurisdiction is represented by a map between the jurisdiction name and an optional JurisdictionRef object, which can be used to specify the display name and display order.

For example:

{
    "jurisdictions": {
        "CA": {
            "displayHints": {
                "displayName": "California",
                "displayOrder": 1
            }
        },
        "FL": {}
    }
}

You can force a product to be associated with a jurisdiction by setting the requiresJurisdiction flag to true in the ProductRef object. Enabling this flag will cause validation requests for quotes and policies without an associated jurisdiction to fail.

For example:

{
    "requiresJurisdiction": true
}

Implementation

Quotes and Policies

Once your configuration changes have been deployed, you can specify the name of a jurisdiction to associate with a quote or policy in the jurisdiction field when using the Socotra API to create or update quotes and policies. Quotes and policies can only be associated with a maximum of one jurisdiction.

Here’s an example of the jurisdiction field when sending a request to the Create a Quote API endpoint:

{
    "jurisdiction": "CA"
}

The Update Policy Jurisdiction API endpoint can be used to update the jurisdiction associated with a policy directly.

Resources

You can specify the name of one or more jurisdictions to associate with resources such as documents, tables, and secrets when using the Socotra API to create or update resources.

Here’s an example of the jurisdiction query parameter when sending a request to the Create a New Document Resource API endpoint:

jurisdiction=CA&jurisdiction=FL

Important

No jurisdiction can appear more than once across resource instances with the same staticName within the same resource group.