*REST API › Endpoint reference › Operations › Incidents*

# Update an incident

> Updates an incident (send only the fields to change).

Lists fully replace the existing one. Costs, the internal resolution note and publication on the customer portal cannot be written here. Returns the updated incident.

`PATCH /api/v1/incidents/{incidentId}` — scope `incidents:write`

Scope: `incidents:write` · 120/min · Add-on (402) · Idempotency-Key · If-Match · MCP: `filmo_incidents_update`

## Authorizations

Bearer API key with the scope below. `incidents:write`

## Headers

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `Idempotency-Key` | string | No | Unique identifier of the request, chosen by the client (a UUID works). Between 1 and 255 characters: an empty header is rejected with 400 `validation_error`, because the client would believe itself protected. Repeating the same key with the SAME body within 24 h returns the stored response without executing again, with the `Idempotent-Replay: true` header. With a DIFFERENT body it returns 422. It is the safe way to retry after a network timeout. |
| `If-Match` | string | No | Optimistic locking: the `ETag` you read from the resource (or `*`). If the resource changed since, the write is rejected with `412 precondition_failed` before doing anything; read it again and retry. Without the header the write always proceeds. |

## Path parameters

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `incidentId` | string | Yes | Incident identifier. |

## Body

Body schema: `IncidentUpdateBody`

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `title` | string | No | Short title. |
| `type` | string | No | Nature of the incident. `damage`, `loss`, `malfunction`, `cosmetic`, `theft`, `custom` |
| `scope` | string | No | What it affects. `item`, `serializedItem`, `space`, `kit`, `vehicle`, `custom` |
| `status` | string | No | Lifecycle status. `draft`, `open`, `waiting`, `repairing`, `complete`, `lost` |
| `priority` | string | No | Priority. `urgent`, `high`, `medium`, `low`, `none` |
| `severity` | string | No | Severity. `low`, `high` |
| `repairType` | string | No | Whether the team repairs it or an external workshop does. `internal`, `external` |
| `description` | string | No | Description. |
| `blocksAvailability` | boolean | No | Whether it removes the material from the pool. |
| `affectedQuantity` | integer | No | Affected units. |
| `itemId` | string | No | Affected item; null unlinks it. |
| `serializedItemId` | string | No | Physical unit; null unlinks it. |
| `variantId` | string | No | Variant; null unlinks it. |
| `spaceId` | string | No | Space; null unlinks it. |
| `vehicleId` | string | No | Vehicle; null unlinks it. |
| `orderId` | string | No | Order; null unlinks it. |
| `projectId` | string | No | Project; null unlinks it. |
| `contactIds` | string[] | No | Involved contacts. Replaces the list. |
| `assigneeStaffIds` | string[] | No | Assigned staff. Replaces the list. |
| `subscriberIds` | string[] | No | Deprecated: accepted for compatibility and ignored. Incidents no longer keep a subscriber list. |
| `labels` | string[] | No | Labels. Replaces the list. |
| `images` | string[] | No | Photos of the damage. Replaces the list. |
| `relatedIncidentIds` | string[] | No | Related incidents. |
| `blockedByIncidentIds` | string[] | No | Incidents that block this one. |
| `dueDate` | string<date-time> | No | Target date, in ISO 8601 with offset; null clears it. |
| `estimatedResolutionDate` | string<date-time> | No | Estimated resolution date, in ISO 8601 with offset; null clears it. |
| `actualResolutionDate` | string<date-time> | No | Actual resolution date, in ISO 8601 with offset; null clears it. |
| `reminderEnabled` | boolean | No | Enables the internal reminder. |
| `reminderDate` | string<date-time> | No | Reminder date, in ISO 8601 with offset; null clears it. |
| `parentIncidentId` | string | No | Parent incident; null unlinks it. |

## Request examples

*Update an incident*

**cURL**

```bash
curl https://app.filmo.io/api/v1/incidents/inci_8f2a1c \
  --request PATCH \
  --header "Authorization: Bearer $FILMO_API_KEY" \
  --header "Idempotency-Key: $(uuidgen 2>/dev/null || cat /proc/sys/kernel/random/uuid)" \
  --header 'Content-Type: application/json' \
  --data '{
  "status": "repairing",
  "repairType": "external",
  "estimatedResolutionDate": "2026-09-25T12:00:00+02:00"
}'
```

**Node.js**

```javascript
fetch('https://app.filmo.io/api/v1/incidents/inci_8f2a1c', {
  method: 'PATCH',
  headers: {
    Authorization: 'Bearer YOUR_FILMO_API_KEY',
    'Idempotency-Key': crypto.randomUUID(),
    'Content-Type': 'application/json'
  },
  body: JSON.stringify({
    status: 'repairing',
    repairType: 'external',
    estimatedResolutionDate: '2026-09-25T12:00:00+02:00'
  })
})
```

**Python**

```python
import uuid
import requests

requests.patch(
    "https://app.filmo.io/api/v1/incidents/inci_8f2a1c",
    headers={
      "Authorization": "Bearer YOUR_FILMO_API_KEY",
      "Idempotency-Key": str(uuid.uuid4()),
      "Content-Type": "application/json"
    },
    json={
      "status": "repairing",
      "repairType": "external",
      "estimatedResolutionDate": "2026-09-25T12:00:00+02:00"
    }
)
```

## Response

Response schema: `IncidentDto`

| Status | Description |
| --- | --- |
| 200 | Successful response. |
| 400 | Invalid request (validation_error): malformed query or body. `errors[]` lists every offending field with its stable code. |
| 401 | Authentication failed (unauthorized, api_key_invalid, api_key_revoked, api_key_expired, api_key_owner_inactive, api_key_owner_not_admin). |
| 402 | Add-on required (addon_required): the account plan does not include the add-on this operation needs; `requiredAddon` names it. |
| 403 | Not allowed (insufficient_scope: the API key does not have the required scope, named in `requiredScope`; forbidden: the owner of the key lacks the permission the operation requires). `insufficient_scope` is answered before the request counts against the rate limit, so it carries no `RateLimit-*` headers; `forbidden` does. |
| 404 | Resource not found (not_found): it does not exist or is outside the scope of the API key. |
| 409 | Conflict (conflict): the current state of the resource prevents the operation, a request with that Idempotency-Key is already in progress, or another conditional write (`If-Match`) held the resource for more than five seconds. `errors[0].code` says which: `in_progress` and `lock_timeout` are solved by retrying; `invalid_state` is not, because the state of the resource forbids the operation. |
| 412 | Precondition failed (precondition_failed): the `If-Match` entity tag does not match the current representation. Read the resource again and retry. |
| 422 | Idempotency-Key reused (idempotency_key_reused): the same key was used before with a different body. Change the key. |
| 429 | Rate limit exceeded (rate_limited): retry after `Retry-After` seconds; `RateLimit-*` says which quota ran out. |
| 500 | Internal error (internal_error). |

**200**

| Name | Type | Description |
| --- | --- | --- |
| `data` | object | Broken, lost or malfunctioning material, with its repair status. |
| `data.id` | string | Unique incident identifier. |
| `data.identifier` | string | Human-readable incident number. |
| `data.title` | string | Short title of the incident. |
| `data.description` | string | Description; null if it has none. |
| `data.type` | string | Nature: damage, loss, malfunction, cosmetic, theft or custom. |
| `data.scope` | string | What it affects: item, serializedItem, space, kit, vehicle or custom. `item`, `serializedItem`, `space`, `kit`, `vehicle`, `custom` |
| `data.status` | string | Lifecycle status: draft, open, waiting, repairing, complete or lost. |
| `data.priority` | string | Priority: urgent, high, medium, low or none. |
| `data.severity` | string | Declared severity. |
| `data.blocksAvailability` | boolean | true when the incident removes the material from the available pool. |
| `data.affectedQuantity` | integer | Affected units in bulk stock; null when not applicable. |
| `data.itemId` | string | Affected item; null if not applicable. |
| `data.serializedItemId` | string | Affected physical unit; null if not applicable. |
| `data.spaceId` | string | Affected space; null if not applicable. |
| `data.vehicleId` | string | Affected vehicle; null if not applicable. |
| `data.orderId` | string | Order in which it was detected; null if not applicable. |
| `data.projectId` | string | Associated project; null if not applicable. |
| `data.dueDate` | string<date-time> | Target resolution date in ISO 8601 UTC; null if it has none. |
| `data.commentCount` | integer | Comments the incident has. |
| `data.createdAt` | string<date-time> | Creation date in ISO 8601 UTC. |
| `data.updatedAt` | string<date-time> | Last modification date in ISO 8601 UTC. |
| `meta` | object | Additional information about the response. |
| `meta.warnings` | object[] | Lifecycle warnings; present only when the operation is deprecated. |
| `meta.warnings.code` | string | Stable warning code. `deprecated` |
| `meta.warnings.message` | string | For people: what is deprecated, until when, and what to use. |
| `meta.warnings.sunset` | string | Day (YYYY-MM-DD) the operation stops being served. |
| `meta.warnings.replacement` | string | `operationId` of the operation to use instead, or null if there is none. |
| `meta.warnings.link` | string | Where the deprecation is documented (the changelog). |

*Example response · 200*

```json
{
  "data": {
    "id": "incident_9f3a2b",
    "identifier": "Example identifier",
    "title": "Example title",
    "description": "Example text.",
    "type": "Example type",
    "scope": "item",
    "status": "Example status",
    "priority": "Example priority",
    "severity": "Example severity",
    "blocksAvailability": true,
    "affectedQuantity": 1,
    "itemId": "item_9f3a2b",
    "serializedItemId": "serialized_item_9f3a2b",
    "spaceId": "space_9f3a2b",
    "vehicleId": "vehicle_9f3a2b",
    "orderId": "order_9f3a2b",
    "projectId": "project_9f3a2b",
    "dueDate": "2026-09-01T08:00:00.000Z",
    "commentCount": 1,
    "createdAt": "2026-09-01T08:00:00.000Z",
    "updatedAt": "2026-09-01T08:00:00.000Z"
  }
}
```

## Errors

| Status | Codes | Meaning |
| --- | --- | --- |
| 400 | `validation_error` | Malformed query or body. `errors[]` lists every offending field with its stable code. |
| 402 | `addon_required` | The account plan does not include the add-on this operation needs; `requiredAddon` names it. |
| 404 | `not_found` | It does not exist or is outside the scope of the API key. |
| 409 | `conflict` | The current state of the resource prevents the operation, a request with that Idempotency-Key is already in progress, or another conditional write (`If-Match`) held the resource for more than five seconds. `errors[0].code` says which: `in_progress` and `lock_timeout` are solved by retrying; `invalid_state` is not, because the state of the resource forbids the operation. |
| 412 | `precondition_failed` | The `If-Match` entity tag does not match the current representation. Read the resource again and retry. |
| 422 | `idempotency_key_reused` | The same key was used before with a different body. Change the key. |

## Deprecation

This operation is not deprecated. Deprecations are announced with a Deprecation header and a sunset date.

---

Canonical URL: https://docs.filmo.io/rest-api/endpoint-reference/incidents/update-an-incident  
Last updated: 2026-10-25