--- title: "Changes to Merge feature requests" method: POST path: "/feature-requests/merge" --- # Changes to Merge feature requests `POST /feature-requests/merge` > Every recorded change to this operation, newest first. ## Timeline Changed in 6 of 63 revisions. - **2026-10-31** `05e40342a893`: 2 info - **2026-10-12** `40bf3229d58f`: 1 info - **2026-10-11** `dfb481067e5a`: 2 breaking, 99 info - **2026-09-12** `e85c0a2a3253`: 4 info - **2026-08-19** `601861c5dfcf`: 2 info - **2026-08-08** `484a11d5ddb2`: 1 info ## Changes - **2026-10-31** `05e40342a893`: 2 info - added the optional property `data/external_issues/items/key` to the response with the `200` status - added the optional property `data/external_issues/items/state` to the response with the `200` status - **2026-10-12** `40bf3229d58f`: 1 info - the response property `data` became required for the status `200` - **2026-10-11** `dfb481067e5a`: 2 breaking, 99 info - the response property `data/custom_fields` became nullable for the status `200` - the response property `data/portal_visible_to_account_ids` 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/evidence/items/created_at` became required for the status `200` - the response property `data/evidence/items/id` became required for the status `200` - the response property `data/evidence/items/source_type` became required for the status `200` - the response property `data/evidence_count` became required for the status `200` - the response property `data/external_issues/items/external_id` became required for the status `200` - the response property `data/external_issues/items/link` became required for the status `200` - the response property `data/external_issues/items/source` became required for the status `200` - the response property `data/id` became required for the status `200` - the response property `data/title` 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 `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` - …61 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-19** `601861c5dfcf`: 2 info - added the optional property `data/evidence/items/created_at` to the response with the `200` status - added the optional property `data/evidence/items/id` to the response with the `200` status - **2026-08-08** `484a11d5ddb2`: 1 info - endpoint added --- [Operation](https://skmtc.dev/usepylon/apis/pylon-api/docs/feature-requests/merge/post.md) - [API](https://skmtc.dev/usepylon/apis/pylon-api.md) - [Page](https://skmtc.dev/usepylon/apis/pylon-api/changes/feature-requests/merge/post)