# Update Serial Number

`PATCH /inventory/serial-numbers/{id}`

Group: Inventory › Serial Numbers · Operation ID: `updateSerialNumber`

Updates the serial number with the given identifier. Only the manufacturer serial number, the expiry and entry dates, and the active flag can be changed.

Only the fields present in the request are written. The cost fields, the stock state and the location are written by the documents that move and value the unit and cannot be sent here.

[Open in the interactive reference](https://docs.api.lensing.ai/?op=updateSerialNumber)

## Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `Api-Version` | header | `"v1"` | yes | The API version this request targets, named by its public identifier. Required on every request; omitting it, or naming a version this company does not have, is answered with 400. This document describes version `v1`. |
| `Idempotency-Key` | header | string | no | An opaque caller-chosen string (1-255 characters) that makes this request safe to retry. Repeating the same key with an identical request body replays the original response instead of re-executing - but only once that original request succeeded; a failed attempt re-executes on retry. Repeating the key with a different body is answered with 422. A key still in flight is answered with 409 - as is a key whose original request was interrupted before it finished, for a few minutes afterwards, until that attempt is presumed dead. A completed response stays replayable for 24 hours. The key is scoped to the caller, not to the action: reusing it for a different action is answered with 409 or 422 rather than treated independently. On read actions this header is ignored. On write actions that cannot offer the guarantee it is answered with `400 IDEMPOTENCY_NOT_SUPPORTED` rather than silently ignored. |
| `id` | path | string | yes | The unique identifier for the serial number to update. |

## Request body

Required, `application/json`: updateSerialNumberInput.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `manufacturerSerialNumber` | string | no | The manufacturer's own serial number for the unit. |
| `expirationDate` | string (date) | no | The date the unit expires. Use format YYYY-MM-DD. |
| `entryDate` | string (date) | no | The date the unit entered the warehouse. Use format YYYY-MM-DD. |
| `active` | boolean | no | Whether the serial number can be selected on new documents. Setting it to false retires the record. Its history stays readable. |

Example:

```json
{
  "manufacturerSerialNumber": "MFG-77-000418",
  "expirationDate": "2026-01-15",
  "entryDate": "2026-01-15",
  "active": true
}
```

## Response

`200` Success

Under `data` (updateSerialNumberOutput):

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `id` | string | yes | The unique identifier for the serial number. |

## Response headers

- `Idempotency-Replayed` — Present and `true` only when this response replays a previously stored one for the same Idempotency-Key, rather than reflecting a live execution. Absent on a live response - never sent as `false`.

## Errors

| Code | Status |
| --- | --- |
| `NOT_FOUND` | 400 |
| `IDEMPOTENCY_KEY_CONFLICT` | 409 |
| `IDEMPOTENCY_PAYLOAD_MISMATCH` | 422 |

## Statuses

- `400` — Invalid request or business failure. Codes: NOT_FOUND
- `401` — Missing or invalid access token
- `403` — Not authorized
- `404` — Not found
- `409` — The Idempotency-Key is still being processed by another request.
- `422` — The Idempotency-Key was already used with a different request payload.
- `429` — Too many requests
- `500` — Internal server error