---
title: "Changes to Create a custom field"
method: POST
path: "/custom-fields"
---

# Changes to Create a custom field

`POST /custom-fields`

> Every recorded change to this operation, newest first.

## Timeline

Changed in 6 of 63 revisions.

- **2026-10-12** `40bf3229d58f`: 1 info
- **2026-10-11** `dfb481067e5a`: 4 breaking, 101 info
- **2026-09-12** `e85c0a2a3253`: 4 info
- **2026-08-28** `fe3adb90ea45`: 1 info
- **2026-08-14** `ad855d921ee9`: 1 breaking, 7 info
- **2026-07-26** `3e347e631c35`: 2 info

## Changes

- **2026-10-12** `40bf3229d58f`: 1 info
  - the response property `data` became required for the status `200`
- **2026-10-11** `dfb481067e5a`: 4 breaking, 101 info
  - the response property `data/number_metadata/currency` became nullable for the status `200`
  - the response property `data/number_metadata/decimal_places` became nullable for the status `200`
  - the response property `data/number_metadata/format` became nullable for the status `200`
  - the response property `data/select_metadata/options` became nullable for the status `200`
  - added the non-success response with the status `401`
  - added the non-success response with the status `429`
  - the response property `data/created_at` became required for the status `200`
  - the response property `data/description` became required for the status `200`
  - the response property `data/id` became required for the status `200`
  - the response property `data/is_read_only` became required for the status `200`
  - the response property `data/label` became required for the status `200`
  - the response property `data/object_type` became required for the status `200`
  - the response property `data/slug` became required for the status `200`
  - the response property `data/source` became required for the status `200`
  - the response property `data/type` became required for the status `200`
  - the response property `data/updated_at` became required for the status `200`
  - the response property `request_id` became required for the status `200`
  - the response property `request_id` became required for the status `400`
  - the response property `request_id` became required for the status `403`
  - the response property `request_id` became required for the status `404`
  - the response property `request_id` became required for the status `500`
  - removed the `currency` enum value from the `data/number_metadata/format` response property for the response status `200`
  - removed the `duplicate_object` enum value from the `code` response property for the response status `400`
  - removed the `duplicate_object` enum value from the `code` response property for the response status `403`
  - removed the `duplicate_object` enum value from the `code` response property for the response status `404`
  - removed the `duplicate_object` enum value from the `code` response property for the response status `500`
  - removed the `duration` enum value from the `data/number_metadata/format` response property for the response status `200`
  - removed the `email_bounced` enum value from the `code` response property for the response status `400`
  - removed the `email_bounced` enum value from the `code` response property for the response status `403`
  - removed the `email_bounced` enum value from the `code` response property for the response status `404`
  - removed the `email_bounced` enum value from the `code` response property for the response status `500`
  - removed the `internal_error` enum value from the `code` response property for the response status `400`
  - removed the `internal_error` enum value from the `code` response property for the response status `403`
  - removed the `internal_error` enum value from the `code` response property for the response status `404`
  - removed the `internal_error` enum value from the `code` response property for the response status `500`
  - removed the `internal_issue_reply_not_allowed` enum value from the `code` response property for the response status `400`
  - removed the `internal_issue_reply_not_allowed` enum value from the `code` response property for the response status `403`
  - removed the `internal_issue_reply_not_allowed` enum value from the `code` response property for the response status `404`
  - removed the `internal_issue_reply_not_allowed` enum value from the `code` response property for the response status `500`
  - removed the `invalid_api_token` enum value from the `code` response property for the response status `400`
  - …65 more
- **2026-09-12** `e85c0a2a3253`: 4 info
  - added the optional property `code` to the response with the `400` status
  - added the optional property `code` to the response with the `403` status
  - added the optional property `code` to the response with the `404` status
  - added the optional property `code` to the response with the `500` status
- **2026-08-28** `fe3adb90ea45`: 1 info
  - added the non-success response with the status `403`
- **2026-08-14** `ad855d921ee9`: 1 breaking, 7 info
  - request property `object_type` was restricted to a list of enum values
  - added the new `account` enum value to the request property `object_type`
  - added the new `contact` enum value to the request property `object_type`
  - added the new `issue` enum value to the request property `object_type`
  - added the new `meeting` enum value to the request property `object_type`
  - added the new `opportunity` enum value to the request property `object_type`
  - added the new `project` enum value to the request property `object_type`
  - added the new `task` enum value to the request property `object_type`
- **2026-07-26** `3e347e631c35`: 2 info
  - added the new optional request property `select_options/items/ai_description`
  - added the optional property `data/select_metadata/options/items/ai_description` to the response with the `200` status

---

[Operation](https://skmtc.dev/usepylon/apis/pylon-api/docs/custom-fields/post.md) - [API](https://skmtc.dev/usepylon/apis/pylon-api.md) - [Page](https://skmtc.dev/usepylon/apis/pylon-api/changes/custom-fields/post)
