---
title: "Batch Update Asset Fields"
method: POST
path: "/v2/assets/fields/batch/update"
tags: ["Routes", "Assets", "Batch"]
---

# Batch Update Asset Fields

`POST /v2/assets/fields/batch/update`

This request will update multiple asset fields values at a time. The request expects an array of asset fields values. The array needs to have atleast two asset field values and atmost 100 asset field values. The request expects an array made up of asset field values that need to be updated. Only asset fields values of type Text (1), Date (2), Number (5) and Currency (6) can be updated using this request.

The response returns `{ sucess:true }` if all field values are updated successfully. The response returns `{ sucess: false }` and an `updates` array that gives details of which field values were updated and the `reason` for field values that were not updated successfully. Please refer to the examples for more information.

valueID | Integer | Required | The valueID of the asset field value
value | Based on the type of value | Required | The value that needs to be updated

## Request body

- object[]
  - `value` string
  - `valueID` integer

## Response `200`

Some field values are not updated.

- object
  - `updates` object[]
    - `value` string
    - `valueID` integer
    - `success` boolean
  - `success` boolean

## Other responses

- `400` — The request was malformed — either invalid JSON syntax or a validation failure (missing required field, wrong type, etc.).
- `401` — No `Authorization` header was provided on the request.
- `403` — The supplied credentials are invalid, the customer account is inactive, or the credentials do not have permission to perform this action.
- `409` — The request conflicts with the current state of the resource (e.g. a uniqueness constraint or a referenced parent that is in the wrong state).
- `429` — The per-minute or per-hour rate limit for this credential and method has been exhausted. Inspect the `X-RateLimit-*` headers to determine when to retry.
- `500` — An unhandled server-side error. The body message is generic (`System unavailable...`) when the underlying cause is a database fault; otherwise it reflects the raised error.

---

[API](https://skmtc.net/limblecmms/apis/limble-api-v2.md) · [All operations](https://skmtc.net/limblecmms/apis/limble-api-v2/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/limblecmms/limble-api-v2/revisions/eceb9442ed4d/schema)