The Fields API allows you to manage fields and field values information. The Fields API is currently in Beta and is available for use. Customers do not need to explicitly opt-in to Beta. However, the API is subject to changes as per the expectations set regarding Beta APIs in the API Launch Stages documentation: https://developer.brex.com/docs/api-launch-stages/.
APIs/Fields//
- Delete a custom field
List custom fields
Create a custom field
Get custom field
Update a custom field
Delete a custom field
Fields API (1.0.0-beta)
Download OpenAPI description
Overview
Languages
Servers
Production
https://api.brex.com
Staging (Note: This is not a sandbox. It will not work with customer tokens.)
https://api-staging.brex.com
Security
OAuth2(Required scopes:
fields.read
fields.write
)- Productionhttps://api.brex.com/v1/fields
- Staging (Note: This is not a sandbox. It will not work with customer tokens.)https://api-staging.brex.com/v1/fields
- curl
- JavaScript
- Node.js
- Python
curl -i -X GET \
https://api.brex.com/v1/fields \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>'Response
application/json
{ "next_cursor": "string", "items": [ { … } ] }
Bodyapplication/jsonrequired
The category of the field, indicating its purpose or context. For example, it could belong to accounting-related fields or user-related fields.
Enum"ACCOUNTING""USER""ERP"
Remote/external ID of custom field from external system (e.g. ERP or HRIS system)
Example: "foo_bar"
Integration ID to associate this field with a specific integration
Example: "int_123"
- Productionhttps://api.brex.com/v1/fields
- Staging (Note: This is not a sandbox. It will not work with customer tokens.)https://api-staging.brex.com/v1/fields
- curl
- JavaScript
- Node.js
- Python
curl -i -X POST \
https://api.brex.com/v1/fields \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>' \
-H 'Content-Type: application/json' \
-H 'Idempotency-Key: string' \
-d '{
"name": "string",
"group": "ACCOUNTING",
"remote_id": "foo_bar",
"integration_id": "int_123",
"is_disabled": true
}'Response
application/json
{ "brex_id": "extended_field_foobar", "name": "string", "remote_id": "foo_bar", "updated_at": "2019-08-24T14:15:22Z", "is_disabled": true, "group": "ACCOUNTING" }
- Productionhttps://api.brex.com/v1/fields/{id}
- Staging (Note: This is not a sandbox. It will not work with customer tokens.)https://api-staging.brex.com/v1/fields/{id}
- curl
- JavaScript
- Node.js
- Python
curl -i -X GET \
https://api.brex.com/v1/fields/extended_field_foobar \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>'Response
application/json
{ "brex_id": "extended_field_foobar", "name": "string", "remote_id": "foo_bar", "updated_at": "2019-08-24T14:15:22Z", "is_disabled": true, "group": "ACCOUNTING" }
- Productionhttps://api.brex.com/v1/fields/{id}
- Staging (Note: This is not a sandbox. It will not work with customer tokens.)https://api-staging.brex.com/v1/fields/{id}
- curl
- JavaScript
- Node.js
- Python
curl -i -X PUT \
https://api.brex.com/v1/fields/extended_field_foobar \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>' \
-H 'Content-Type: application/json' \
-d '{
"name": "string",
"is_disabled": true
}'Response
application/json
{ "brex_id": "extended_field_foobar", "name": "string", "remote_id": "foo_bar", "updated_at": "2019-08-24T14:15:22Z", "is_disabled": true, "group": "ACCOUNTING" }
- Productionhttps://api.brex.com/v1/fields/{id}
- Staging (Note: This is not a sandbox. It will not work with customer tokens.)https://api-staging.brex.com/v1/fields/{id}
- curl
- JavaScript
- Node.js
- Python
curl -i -X DELETE \
https://api.brex.com/v1/fields/extended_field_foobar \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>'