---
title: "Update a custom field"
method: PUT
path: "/v1/fields/{id}"
tags: ["Fields"]
---

# Update a custom field

`PUT /v1/fields/{id}`

Update a field by ID

## Path parameters

- `id` string, required

## Request body

- FieldUpdateBody — Represents the data needed to update a field
  - `name` string, nullable — The name of the field
  - `is_disabled` boolean, nullable — Indicates whether the field is disabled. A disabled field is not selectable: it is no longer offered as an option in the Brex dropdown and cannot be applied to new transactions. Records that already reference the field are unaffected.

## Response `200`

Update custom field response

- Field — Represents a field definition
  - `brex_id` string, required — The internal Brex ID of the field
  - `name` string, nullable, required — The name of the field
  - `remote_id` string, nullable — Remote/external ID of custom field from external system (e.g. ERP or HRIS system)
  - `updated_at` string, date-time, required — The last updated timestamp of the field
  - `is_disabled` boolean, required — Indicates whether the field is disabled. A disabled field is not selectable: it is no longer offered as an option in the Brex dropdown and cannot be applied to new transactions. Records that already reference the field are unaffected.
  - `group` 'ACCOUNTING' | 'USER' | 'ERP' | 'TRAVEL', nullable — The category of the field, indicating its purpose or context. For example, it could belong to accounting-related fields or user-related fields.

## Other responses

- `400` — Bad request
- `401` — Unauthorized
- `403` — Forbidden
- `404` — Not found
- `500` — Internal server error

---

[API](https://skmtc.net/brex-com/apis/fields-api.md) · [All operations](https://skmtc.net/brex-com/apis/fields-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/brex-com/fields-api/versions/b1ba15754f28/schema)