---
title: "Update Job Insurance"
method: PUT
path: "/jobs/{jobId}/insurance"
tags: ["jobs"]
---

# Update Job Insurance

`PUT /jobs/{jobId}/insurance`

This endpoint sets the insurance information for an existing job.
- "Insurance company" section:
  It can be set by ID or by name, but not both.
  The ID should belong to the existing insurance companies. If the name is used it will be assigned to "Other" (active) insurance company.
  Set them as not assigned can be done, just sending both(ID & name) null or empty will do it.
- dateOfLoss & claimFiledDate should be UTC and in ISO 8601 format (suffixed with 'Z').

This endpoint is rate limited. Use the `RateLimit-*` response headers to check current limits and remaining quota.

## Path parameters

- `jobId` string, uuid, required

## Request body

- JobInsurancePut
  - `insuranceCompany` object
    - `insuranceCompanyId` string, uuid, nullable — The insurance company's unique ID is to be set to the job.
    - `insuranceCompanyName` string, nullable — A job can have an insurance company that is not from the list managed in Account Settings. In this case, the 'insuranceCompanyId' should be null. The text will be assigned to the comments field for the 'Other' (active) insurance company.
    - `id` string, uuid — An unique identifier for the insurance company.
    - `name` string — Name of the insurance company.
  - `_link` string, uri
  - `claimFiled` boolean — Indicates if the claim was filed or not.
  - `claimFiledDate` string, date-time — Date when the claim was filed.
  - `claimNumber` string — An identifier for the claim.
  - `customInsuranceCompanyName` string — A name for a custom insurance company
  - `damageLocation` string — A string representing data about the location of the damage.
  - `dateOfLoss` string, date-time — The date of loss registered for the insurance.
  - `hasPaperwork` boolean — Indicates if the insurance has paperwork.

## Response `204`

No Content

## Other responses

- `400` — Bad Request - The server cannot process the request due to a client error. Common causes: - Invalid request format - Missing required fields - Validation errors in the request data
- `401` — Unauthorized - Authentication is required or has failed. Common causes: - Missing API key - Invalid API key - Expired or deactivated API key
- `404` — Not Found - The requested resource does not exist. Common causes: - Invalid subscription ID - Subscription has been deleted - URL path contains typos or incorrect values
- `429` — Too Many Requests

---

[API](https://skmtc.net/acculynx/apis/acculynx-api-v2.md) · [All operations](https://skmtc.net/acculynx/apis/acculynx-api-v2/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/acculynx/acculynx-api-v2/revisions/3a9e3886e400/schema)