---
title: "Update System Metadata"
method: PATCH
path: "/api/v1/setup/metadata"
tags: ["v1", "setup", "factory"]
---

# Update System Metadata

`PATCH /api/v1/setup/metadata`

Update system identification metadata fields.

**Metadata vs Configuration:**
- **Metadata**: Identification fields (chassis type, location, etc.)
- **Configuration**: Operational hardware settings (requires setup mode)

**Chassis Type Notes:**
- Setting to 'user' marks chassis as not yet determined
- Allows completing setup while deferring chassis identification
- Can be updated later without re-entering setup mode

**Does Not Require Setup Mode** - these are non-operational fields.

## Request body

- SystemMetadataUpdate — Request model for updating system identification metadata. These are non-operational identification fields that can be updated outside of setup mode since they don't affect hardware behavior.
  - `chassis_type` 'croc_mini' | 'croc_xl' | 'kronos' | 'caiman' | 'user', nullable — Cable reel chassis type identifier. **Valid Chassis Types:** - **croc_mini** - Compact design for smaller USVs - **croc_xl** - Extended capacity model - **kronos** - High-performance variant - **caiman** - Heavy-duty configuration - **user** - Not yet determined/configured **Usage**: For tracking, support, and maintenance records **Note**: Setting to 'user' indicates the chassis type has not been determined yet. This allows deferring the chassis type decision while completing other setup steps.

## Response `200`

Metadata update result with list of updated fields

- SystemMetadataResponse — Response from system metadata update operation.
  - `success` boolean, required — Whether the metadata update was successful
  - `updated_fields` string[], required — List of metadata fields that were successfully updated
  - `message` string, nullable — Additional information about the update operation

## Other responses

- `400` — Invalid metadata field or value
- `422` — Validation Error
- `500` — Internal server error during setup operation

---

[API](https://skmtc.net/reach-systems-tech/apis/reelapi-v1.md) · [All operations](https://skmtc.net/reach-systems-tech/apis/reelapi-v1/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/reach-systems-tech/reelapi-v1/versions/1dd366a9c6a3/schema)