Subrogation summaries and subrogations

Subrogation occurs when a claim's fault rating is determined to be third-party, and an insurer collects money from the third-party's insurer. For example, in a personal auto collision claim, the policyholder is not at fault, but the driver of the other vehicle is at fault.

Each claim (or exposure) can be associated with multiple subrogations. This is implemented in the data model as an array of subrogation entities. The purpose of a subrogation summary is to compile all information for all subrogations on a claim.

Note: Subrogation summaries and subrogations are two distinct entities in ClaimCenter.

Each claim has at most one subrogation summary. You cannot create or modify subrogation summaries on closed or archived claims. Each subrogation summary has at least one subrogation. No two subrogations can be associated with the same exposure. A subrogation summary can only contain either claim-level subrogations or exposure subrogations, but not both.

A subrogation at the claim level is not associated with an exposure and therefore its exposure is null.

You can query for, create, and modify subrogation summaries through Cloud API.

You can query for, create, delete, and modify subrogations through Cloud API.

Note: In the base application, ClaimCenter provides Gosu Preupdate rules that automatically create subrogation summaries and perform other actions related to subrogation summaries and subrogations. See Gosu Rules Guide.

Use Cloud API to create and manage these entities directly if you do not wish to rely on these rules or if these rules are disabled.

Permissions

Internal and service users possess the necessary permissions to work with subrogation summaries and subrogations. The permissions needed are:

viewsubrodetails
editsubrodetails

Querying for subrogation summaries

Use the following endpoint to retrieve all subrogation summaries for a claim assigned to the user you authenticated as:

GET /claims/{claimId}/subrogation-summaries

Use the following endpoint to retrieve a single subrogation summary:

GET /claims/{claimId}/subrogation-summaries/{subrogationSummaryId}

For example, the following query returns information about subrogation summary cc:ShDb-eMrs2jXFU9wVP1lI:

Command

GET claim/v1/claims/demo_sample:2/subrogation-summaries/cc:ShDb-eMrs2jXFU9wVP1lI

Response

{
    "data": {
        "attributes": {
            "calculateOSRecReserve": false,
            "escalateSubro": false,
            "extOwned": false,
            "id": "cc:ShDb-eMrs2jXFU9wVP1lI",
            "prorateDeductible": true
        },

POSTing subrogation summaries

Use the following endpoint to POST a subrogation summary:

POST /claims/{claimId}/subrogation-summaries

You cannot create a subrogation summary if a claim already has a subrogation summary.

To create a subrogation summary, at the minimum, include an empty request body:

{
  "data": {
    "attributes":
    {  
    }
  }
}

Note: This empty subrogation summary is populated with a claim-level subrogation summary by Claim Preupdate rules in the base application.

PATCHing subrogation summaries

Use the following endpoint to PATCH a subrogation summary:

PATCH /claims/{claimId}/subrogation-summaries/{subrogationSummaryId}

For example, the following modifies the subrogation summary cc:S8hhnDOsOrkptsxm94kG0 to set the deductible to prorated. The prorateDeductible field is a Boolean value indicating whether the deductible is prorated as a result of the subrogation investigation:

Command

PATCH claim/v1/claims/demo_sample:20/subrogation-summaries/cc:S8hhnDOsOrkptsxm94kG0

Request

{
  "data": {
    "attributes": {
        "prorateDeductible": true
      }
     }
}

Response

{
    "data": {
        "attributes": {
            "calculateOSRecReserve": false,
            "escalateSubro": true,
            "extOwned": false,
            "id": "cc:S8hhnDOsOrkptsxm94kG0",
            "prorateDeductible": true,
            "subroReferralComment": "Pursue?",
            "subroReferralDate": "2025-03-04T01:10:39.162Z"
        },
        "checksum": "2",
        "links": {
            "self": {
                "href": "/claim/v1/claims/demo_sample:20/subrogation-summaries/cc:S8hhnDOsOrkptsxm94kG0",
                "methods": [
                    "get",
                    "patch"
                ]
            },
            "subrogations": {
                "href": "/claim/v1/claims/demo_sample:20/subrogation-summaries/cc:S8hhnDOsOrkptsxm94kG0/subrogations",
                "methods": [
                    "get",
                    "post"
                ]
            }
        }
    }
}

You can query for, create, modify, and delete subrogations through Cloud API.

Querying for subrogations

Use the following endpoint to retrieve all subrogations for a claim assigned to the user you authenticated as:

GET /claims/{claimId}/subrogation-summaries/{subrogationSummaryId}/subrogations

Use the following endpoint to retrieve a single subrogation:

GET /claims/{claimId}/subrogation-summaries/{subrogationSummaryId}/subrogations/{subrogationId}

POSTing subrogations

A subrogation can be associated with an exposure or a claim.

Exposure-level subrogation

You must include an exposure-level object in the request:

 "exposure": {
        "id": "exposureId"
      }

Claim-level subrogation

You must set the exposure to null in the request:

"exposure": null

Use the following endpoint to POST a subrogation:

POST /claims/{claimId}/subrogation-summaries/{subrogationSummaryId}/subrogations

The following example creates a subrogation associated with the subrogation summary cc:S8hhnDOsOrkptsxm94kG0 with the minimal amount of information (an exposure on the claim with id demo_sample:10003):

Command

POST claim/v1/claims/demo_sample:20/subrogation-summaries/cc:S8hhnDOsOrkptsxm94kG0/subrogations

Request

{
  "data": {
    "attributes":
    {
        "exposure":{
            "id": "demo_sample:10003"
        }
    }
  }
}

Response

{
    "data": {
        "attributes": {
            "assignmentDate": "2025-03-11T23:19:26.896Z",
            "assignmentStatus": {
                "code": "assigned",
                "name": "Assigned"
            },
            "exposure": {
                "displayName": "(1) 1st Party Vehicle - Robert Farley",
                "id": "demo_sample:10003",
                "type": "Exposure",
                "uri": "/claim/v1/claims/demo_sample:20/exposures/demo_sample:10003"
            },
            "id": "cc:SwsNyhhVyBPxdsfAptFpm"
        },
        "checksum": "0",
        "links": {
            "self": {
                "href": "/claim/v1/claims/demo_sample:20/subrogation-summaries/cc:S8hhnDOsOrkptsxm94kG0/subrogations/cc:SwsNyhhVyBPxdsfAptFpm",
                "methods": [
                    "delete",
                    "get",
                    "patch"
                ]
            }
        }
    }
}

PATCHing subrogations

You can modify an existing subrogation. In many cases, this involves closing an open subrogation.

For example, the following PATCH request closes the subrogation cc:S3cXMR9WDShUxXGTUxFrD:

Command

PATCH claim/v1/claims/demo_sample:1/subrogation-summaries/cc:SiBOVYM8sahODM3Ix-pQi/subrogations/cc:S3cXMR9WDShUxXGTUxFrD

Request

{
  "data": {
    "attributes": {
      "closeComment": "this is a comment",
      "closeDate": "2025-03-03T00:00:00.000Z",
      "outcome": {
        "code": "notpursued"
      },
      "status": {
        "code": "closed"
      }
    }
  }
}

Response

{
    "data": {
        "attributes": {
            "assignmentStatus": {
                "code": "unassigned",
                "name": "Unassigned"
            },
            "closeComment": "this is a comment",
            "closeDate": "2025-03-04T01:25:16.494Z",
            "id": "cc:S3cXMR9WDShUxXGTUxFrD",
            "outcome": {
                "code": "notpursued",
                "name": "Not Pursued"
            },
            "status": {
                "code": "closed",
                "name": "Closed"
            }
        },
        "checksum": "1",
        "links": {
            "self": {
                "href": "/claim/v1/claims/demo_sample:1/subrogation-summaries/cc:SiBOVYM8sahODM3Ix-pQi/subrogations/cc:S3cXMR9WDShUxXGTUxFrD",
                "methods": [
                    "delete",
                    "get",
                    "patch"
                ]
            }
        }
    }
}

Deleting subrogations

You can remove (delete) a subrogation.

Use the following endpoint to DELETE a subrogation:

DELETE /claims/{claimId}/subrogation-summaries/{subrogationSummaryId}/subrogations/{subrogationId}

For example, the following removes the subrogation with id cc:SKAgdMnEVh-cBOxctrEgQ:

Command

DELETE claim/v1/claims/demo_sample:2/subrogation-summaries/cc:ShDb-eMrs2jXFU9wVP1lI/subrogations/cc:SKAgdMnEVh-cBOxctrEgQ