---
title: "Attach Field to Asset"
method: PUT
path: "/v2/assets/{assetID}/fields"
tags: ["Routes", "Assets", "Fields"]
---

# Attach Field to Asset

`PUT /v2/assets/{assetID}/fields`

This request attaches a Suggested Field to an Asset. The field and asset must belong to the same location.

For example, let's say I have an Asset called Truck - 001. This Truck doesn't have any Fields attached to it, but I want to track its Make so I can set that this Truck is a Dodge. This is the request I would use to attach the Make Field to the Truck and then I would use the Update Asset Field Value request to set it to Dodge.

Parameter: locationID, Type: Int, Required?: Required, Description: The ID of the Location the Asset exists at.
Parameter: fieldID, Type: Int, Required?: Required, Description: The ID of the existing Field to add to the Asset.

## Response `200`

Attach Field to Asset

- object
  - `valueID` string, utc-millisec

## 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.
- `404` — The referenced resource does not exist or is not visible to the authenticated customer.
- `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/versions/20801e23f7f2/schema)