---
title: "Update an accessory asset"
method: PUT
path: "/api/v2/assets/accessories/{id}"
tags: ["Assets"]
---

# Update an accessory asset

`PUT /api/v2/assets/accessories/{id}`

## Request

- Base URL: `https://console.jumpcloud.com`
- URL: `https://console.jumpcloud.com/api/v2/assets/accessories/{id}`
- Auth: API key in header `x-api-key`
- TypeScript: <https://skmtc.dev/jumpcloud/apis/jumpcloud-console-api/docs/api/v2/assets/accessories/:id/put.ts> (a function with typed inputs; its response is checked against the schema)

Update an existing accessory asset by its ID

## Path parameters

- `id` string, required

## Request body

- JumpcloudHttpAssetsUpdateAssetRequest: Request payload for updating an existing asset of any type
  - `fields` object, required: Asset field values organized by field label to update

## Response `200`

Accessory asset updated successfully

- JumpcloudHttpAssetsAsset: Generic asset representation with field values. Each `fields` value is a `FieldValue` (`editable` plus typed `value`); see the API overview for how `value` is encoded by field type.
  - `id` string, required: The unique identifier of the asset
  - `jcSystemId` string: JumpCloud system identifier for device assets, as a lowercase hex string.
  - `fields` object, required: Asset field values keyed by field label (`FieldValue` per key). Labels match `GET /assets/field-configurations`.

## Other responses

- `400`: Bad request - invalid data or ID format
- `401`: Unauthorized - authentication required
- `404`: Accessory asset not found
- `default`: Generic error response

---

[API](https://skmtc.dev/jumpcloud/apis/jumpcloud-console-api.md) - [All operations](https://skmtc.dev/jumpcloud/apis/jumpcloud-console-api/llms.txt) - [OpenAPI document](https://skmtc.dev/jumpcloud/apis/jumpcloud-console-api/revisions/f396d9271b46?raw)