*REST API › Endpoint reference › Catalog & inventory › Items*

# Update a serialized item

> Changes the record of ONE serialized item: its status, where it is, its serial number or its warranty.

It is what a warehouse system needs to say "this one is back and operational". What the unit cost, the internal note and the subrent terms neither go in nor come out through this API. The item it belongs to is resolved by the server. Returns the full serialized item, the same projection as its GET.

`PATCH /api/v1/serialized-items/{serializedItemId}` — scope `items:write`

Scope: `items:write` · 120/min · Strict tenancy · Idempotency-Key · If-Match · MCP: `filmo_serialized_items_update`

## Authorizations

Bearer API key with the scope below. `items: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 |
| --- | --- | --- | --- |
| `serializedItemId` | string | Yes | Serialized item identifier. |

## Body

Body schema: `SerializedItemUpdateBody`

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `code` | string | No | Internal code of the unit. It identifies the unit, so it cannot be empty. |
| `serialNumber` | string | No | Manufacturer serial number; null clears it. |
| `status` | string | No | Unit status. `available`, `prepared`, `picked_up`, `returned`, `broken`, `archived`, `sold` |
| `active` | boolean | No | false removes the unit from the pool without deleting it. |
| `orderInfo` | string | No | Information visible on the order and on the delivery note. |
| `providerReference` | string | No | Reference by which the supplier identifies the unit. |
| `poNumber` | string | No | Number of the purchase order that brought it in. |
| `purchaseDate` | string<date-time> | No | Purchase date, in ISO 8601 with offset. |
| `warrantyExpiration` | string<date-time> | No | Warranty end, in ISO 8601 with offset. |
| `spaceId` | string | No | Warehouse where the unit is located. |
| `locationId` | string | No | Location within the warehouse; null clears it. |

## Request examples

*Update a serialized item*

**cURL**

```bash
curl https://app.filmo.io/api/v1/serialized-items/seri_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": "available",
  "active": true,
  "spaceId": "spc_almacen_central",
  "locationId": "loc_estante_b3",
  "orderInfo": "Revisada tras la reparación de septiembre"
}'
```

**Node.js**

```javascript
fetch('https://app.filmo.io/api/v1/serialized-items/seri_8f2a1c', {
  method: 'PATCH',
  headers: {
    Authorization: 'Bearer YOUR_FILMO_API_KEY',
    'Idempotency-Key': crypto.randomUUID(),
    'Content-Type': 'application/json'
  },
  body: JSON.stringify({
    status: 'available',
    active: true,
    spaceId: 'spc_almacen_central',
    locationId: 'loc_estante_b3',
    orderInfo: 'Revisada tras la reparación de septiembre'
  })
})
```

**Python**

```python
import uuid
import requests

requests.patch(
    "https://app.filmo.io/api/v1/serialized-items/seri_8f2a1c",
    headers={
      "Authorization": "Bearer YOUR_FILMO_API_KEY",
      "Idempotency-Key": str(uuid.uuid4()),
      "Content-Type": "application/json"
    },
    json={
      "status": "available",
      "active": True,
      "spaceId": "spc_almacen_central",
      "locationId": "loc_estante_b3",
      "orderInfo": "Revisada tras la reparación de septiembre"
    }
)
```

## Response

Response schema: `SerializedItemDetailDto`

| 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). |
| 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 | The serialized item in full, as returned by the API. |
| `data.id` | string | Unique identifier of the physical unit. |
| `data.code` | string | Internal code of the unit. |
| `data.serialNumber` | string | Manufacturer serial number; null if not registered. |
| `data.status` | string | Current status of the unit within the inventory cycle. |
| `data.itemId` | string | Identifier of the catalog item this unit belongs to. |
| `data.itemName` | string | Name of the catalog item. |
| `data.itemSku` | string | SKU of the item; null if it has none. |
| `data.itemCollectionName` | string | Name of the collection of the item; null if it is in none. |
| `data.createdAt` | string<date-time> | Creation date in ISO 8601 UTC; null if not recorded. |
| `data.updatedAt` | string<date-time> | Last modification date in ISO 8601 UTC; null if not recorded. |
| `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": "serialized_item_9f3a2b",
    "code": "Example code",
    "serialNumber": "2026-0001",
    "status": "Example status",
    "itemId": "item_9f3a2b",
    "itemName": "Example item name",
    "itemSku": "Example item sku",
    "itemCollectionName": "Example item collection name",
    "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. |
| 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/items/update-a-serialized-item  
Last updated: 2026-10-25