--- title: "Changes to Search for custom objects by a given filter" method: POST path: "/custom-objects/{type}/search" --- # Changes to Search for custom objects by a given filter `POST /custom-objects/{type}/search` > Every recorded change to this operation, newest first. ## Timeline Changed in 6 of 63 revisions. - **2026-11-01** `8522e66913b4`: 5 info - **2026-10-11** `dfb481067e5a`: 2 breaking, 95 info - **2026-09-12** `e85c0a2a3253`: 4 info - **2026-09-10** `8a1a71062385`: 3 info - **2026-08-28** `fe3adb90ea45`: 1 info - **2026-08-18** `b387b041ea8e`: 1 info ## Changes - **2026-11-01** `8522e66913b4`: 5 info - added the new `not` enum value to the request property `filter/operator` - added the new `time_is_in_last` enum value to the request property `filter/operator` - added the new `time_is_in_next` enum value to the request property `filter/operator` - added the new `time_is_not_in_last` enum value to the request property `filter/operator` - added the new `time_is_not_in_next` enum value to the request property `filter/operator` - **2026-10-11** `dfb481067e5a`: 2 breaking, 95 info - the response property `data/items/custom_fields` became nullable for the status `200` - the response property `data/items/relations` 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` became required for the status `200` - the response property `data/items/created_at` became required for the status `200` - the response property `data/items/id` became required for the status `200` - the response property `data/items/name` became required for the status `200` - the response property `data/items/relations/items/object_id` became required for the status `200` - the response property `data/items/relations/items/object_type` became required for the status `200` - the response property `data/items/type` became required for the status `200` - the response property `data/items/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 `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 `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` - removed the `invalid_api_token` enum value from the `code` response property for the response status `403` - removed the `invalid_api_token` enum value from the `code` response property for the response status `404` - removed the `invalid_api_token` enum value from the `code` response property for the response status `500` - removed the `invalid_authorization_header` enum value from the `code` response property for the response status `400` - removed the `invalid_authorization_header` enum value from the `code` response property for the response status `403` - removed the `invalid_authorization_header` enum value from the `code` response property for the response status `404` - …57 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-09-10** `8a1a71062385`: 3 info - added the new `ends_with` enum value to the request property `filter/operator` - added the new `includes_all_of` enum value to the request property `filter/operator` - added the new `starts_with` enum value to the request property `filter/operator` - **2026-08-28** `fe3adb90ea45`: 1 info - added the non-success response with the status `403` - **2026-08-18** `b387b041ea8e`: 1 info - the request property `filter/field` became optional --- [Operation](https://skmtc.dev/usepylon/apis/pylon-api/docs/custom-objects/:type/search/post.md) - [API](https://skmtc.dev/usepylon/apis/pylon-api.md) - [Page](https://skmtc.dev/usepylon/apis/pylon-api/changes/custom-objects/:type/search/post)