---
title: "Create a custom field"
method: POST
path: "/v1/fields"
tags: ["Fields"]
---

# Create a custom field

`POST /v1/fields`

Create a custom field

## Headers

- `Idempotency-Key` string, required

## Request body

- FieldCreateBody — Represents the data needed to create a field. To create a field in the `ERP` group you must first set up an Accounting Integration and supply its `integration_id`.
  - `name` string, required — The name of the field
  - `group` 'ACCOUNTING' | 'USER' | 'ERP' | 'TRAVEL', required — The category of the field, indicating its purpose or context. For example, it could belong to accounting-related fields or user-related fields.
  - `remote_id` string, nullable — Remote/external ID of custom field from external system (e.g. ERP or HRIS system)
  - `integration_id` string, nullable — The ID of the Accounting Integration to associate this field with. This property is **required** when `group` is `ERP`: it must reference an existing Accounting Integration, and requests that omit it or send `null` for an `ERP` field are rejected. For all other groups (`ACCOUNTING`, `USER`, `TRAVEL`) `integration_id` is not applicable and should be left null.
  - `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`

Create 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.dev/brex-com/apis/fields-api.md) · [All operations](https://skmtc.dev/brex-com/apis/fields-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/brex-com/fields-api/revisions/b1ba15754f28/schema)