*REST API › Endpoint reference › Operations › Incidents*

# Get an incident

> Returns an incident by its identifier: what broke, what it falls on, which status it is in and whether it blocks the availability of the material.

It does NOT include the repair cost or the internal resolution note.

`GET /api/v1/incidents/{incidentId}` — scope `incidents:read`

Scope: `incidents:read` · 120/min · Add-on (402) · If-None-Match · MCP: `filmo_incidents_get`

## Authorizations

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

## Headers

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `If-None-Match` | string | No | Conditional read: the `ETag` of the copy you already have. If the resource has not changed, the response is `304` with no body. |

## Path parameters

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

## Request examples

*Get an incident*

**cURL**

```bash
curl https://app.filmo.io/api/v1/incidents/inci_8f2a1c \
  --header "Authorization: Bearer $FILMO_API_KEY"
```

**Node.js**

```javascript
fetch('https://app.filmo.io/api/v1/incidents/inci_8f2a1c', {
  headers: {
    Authorization: 'Bearer YOUR_FILMO_API_KEY'
  }
})
```

**Python**

```python
import requests

requests.get(
    "https://app.filmo.io/api/v1/incidents/inci_8f2a1c",
    headers={
      "Authorization": "Bearer YOUR_FILMO_API_KEY"
    }
)
```

## Response

Response schema: `IncidentDto`

| Status | Description |
| --- | --- |
| 200 | Successful response. |
| 304 | Not modified: the `If-None-Match` sent matches the current `ETag`. No body; the copy you have is current. |
| 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. |
| 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"
  }
}
```

304: No body.

## Errors

| Status | Codes | Meaning |
| --- | --- | --- |
| 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. |

## 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/get-an-incident  
Last updated: 2026-10-25