coverages

add_coverage

add_coverages

add_sub_lines

delete_coverage

delete_sub_line

list_all_coverages

Code
Get coverages for a specific container with pagination.

Request/response schemas are located at
lib/api/api_specs/request-list_container_coverages_summary.json and
lib/api/api_specs/response-list_container_coverages_summary.json.

Request (Policy Wide):
    {
        "quote_id": "quote1",
        "query": "Coverage C",  # optional
        "pagination": {"page": 1, "page_size": 100}
    }

Request (Property):
    {
        "property_id": "prop1",
        "query": "Coverage C",  # optional
        "pagination": {"page": 1, "page_size": 100}
    }

Response:
    {
        "container_id": "quote1",
        "coverages": [...],
        "pagination": {"page", "page_size", "total_count", "total_pages"}
    }

Code
List containers (Policy Wide and Properties) that have coverages matching the query.

Request/response schemas are located at
lib/api/api_specs/request-list_containers.json and
lib/api/api_specs/response-list_containers.json.

Request:
    {
        "quote_id": "quote1",
        "query": "Coverage C"  # optional
    }

Response:
    {
        "containers": [
            {
                "type": "policy_wide",
                "id": "quote1",
                "name": "Policy Wide",
                "coverage_count": 3
            },
            {
                "type": "property",
                "id": "prop1",
                "name": "Location 1",
                "address": "123 Main Street",
                "coverage_count": 10
            }
        ]
    }

list_coverages

list_sub_lines

update_coverage

update_coverages

Code
Stage a billing-schedule change on an open revision (rating-driven Builder flow).

For rating-driven policy types this also records the admin's preserve/regenerate
choice (regenerate_installments) on revisions.regenerateInstallmentsOnCommit,
consumed at commit by build_installments (BC-22886). The change is not applied
to the policy term until the revision is committed.

Request/response schemas are located at
lib/api/api_specs/request-update_revision_billing_schedule.json and
lib/api/api_specs/response-update_revision_billing_schedule.json.

Request:
    {
        "policy_id": "<uuid>",
        "billing_schedule_id": "<uuid>",
        "revision_id": "<uuid>",
        "regenerate_installments": true  # optional: true=regenerate, false=preserve,
                                         # omitted/null=no decision recorded (preserve)
    }

Response:
    {"success": true, "messages": [], "data": null}