--- title: "Changes to Create a thread on an issue" method: POST path: "/issues/{id}/threads" --- # Changes to Create a thread on an issue `POST /issues/{id}/threads` > Every recorded change to this operation, newest first. ## Timeline Changed in 5 of 63 revisions. - **2026-10-12** `40bf3229d58f`: 1 breaking, 8 info - **2026-10-11** `dfb481067e5a`: 2 breaking, 6 warning, 88 info - **2026-09-12** `e85c0a2a3253`: 4 info - **2026-08-28** `fe3adb90ea45`: 1 info - **2026-08-18** `b387b041ea8e`: 2 info ## Changes - **2026-10-12** `40bf3229d58f`: 1 breaking, 8 info - the `data` response's property type changed from no type to `object` for status `200` - added the optional property `data/channel_id` to the response with the `200` status - added the optional property `data/source` to the response with the `200` status - added the optional property `data/thread_id` to the response with the `200` status - removed `#/components/schemas/IssueThread` from the `data` response property `allOf` list for the response status `200` - the response property `data` became required for the status `200` - added the required property `data/id` to the response with the `200` status - added the required property `data/issue_id` to the response with the `200` status - added the required property `data/name` to the response with the `200` status - **2026-10-11** `dfb481067e5a`: 2 breaking, 6 warning, 88 info - the response property `data` became nullable for the status `200` - the `data` response's property type changed from `object` to no type for status `200` - removed the optional property `data/channel_id` from the response with the `200` status - removed the optional property `data/id` from the response with the `200` status - removed the optional property `data/issue_id` from the response with the `200` status - removed the optional property `data/name` from the response with the `200` status - removed the optional property `data/source` from the response with the `200` status - removed the optional property `data/thread_id` from the response with the `200` status - added the non-success response with the status `401` - added the non-success response with the status `429` - added `#/components/schemas/IssueThread` to the `data` response property `allOf` list for the response 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` - removed the `invalid_authorization_header` enum value from the `code` response property for the response status `500` - …56 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-18** `b387b041ea8e`: 2 info - added the new optional request property `slack_channel_id` - added the new optional request property `slack_thread_ts` --- [Operation](https://skmtc.dev/usepylon/apis/pylon-api/docs/issues/:id/threads/post.md) - [API](https://skmtc.dev/usepylon/apis/pylon-api.md) - [Page](https://skmtc.dev/usepylon/apis/pylon-api/changes/issues/:id/threads/post)