---
title: "New Asset Suggested Field"
method: POST
path: "/v2/assets/fields"
tags: ["Routes", "Assets", "Fields"]
---

# New Asset Suggested Field

`POST /v2/assets/fields`

This request creates a new Suggested Field.

Suggested Fields are the full list of possible Fields that can be added to Assets at that Location.

Parameter: locationID, Type: Int, Required?: Required, Description: The location ID of the Asset to add the new Field to.
Parameter: name, Type: String, Required?: Required, Description: The name of the new Field. Some custom field names such as "Asset" are not allowed and reserved for internal use. This will result in a 409 error.
Parameter: fieldType, Type: Int, Required?: Required, Description: The type of the new Field. You can choose from Text (1), Date (2), Pictures (3), Documents (4), Number (5), Currency (6), Dropdown (7).

Parameter: options, Type: Array of objects with a "name" property, Required?: Optional (only valid when fieldType is 7), Description: Initial list of options for a Dropdown field. Each option must have a "name" string.

## Response `201`

New Asset Suggested Field

- object
  - `fieldID` string, color

## 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/20801e23f7f2/schema)