Creating contingencies

Minimum creation criteria

At a minimum, a contingency must specify:

• A title
• A description
• A dueDate
• An action, which must be set to a typecode from the ContingencyAction typelist

For example, the following request creates a new contingency for policy pc:62 with the given title and description. The due date is November 11, 2021. If the contingency is not resolved by then, PolicyCenter will take the action of retroactively changing the policy (to remove the good driver discount).

POST /policy/v1/policies/pc:62/contingencies

{
  "data": {
    "attributes": {
      "action": {
        "code": "ChangeRetroactively"
      },
      "description": "Driving record required for good driver discount",
      "dueDate": "2021-11-11T00:00:00.000Z",
      "title": "Driving record required"
    }
  }
}

Creating related objects

Use the following endpoint to create activities, documents, and notes for a contingency.

Contingencies associated with jobs

Contingencies associated with policies

When an activity is created directly for an account, job, or policy, you must specify an activity pattern. However, when an activity is created for a contingency, you must omit the activity pattern. All activities created through contingencies use the "New Contingency" activity pattern (uw_review_contingency). If the request payload contains an activity pattern, the request fails.

For more information on working with activities, documents, or notes, see the following:

• Activities
• Documents
• Notes