--- title: "Changes to Create or update a draft reply" method: POST path: "/issues/{id}/draft-reply" --- # Changes to Create or update a draft reply `POST /issues/{id}/draft-reply` > Every recorded change to this operation, newest first. ## Timeline Changed in 5 of 63 revisions. - **2026-10-17** `0e9a6f94eff0`: 3 info - **2026-10-12** `40bf3229d58f`: 1 breaking, 7 info - **2026-10-11** `dfb481067e5a`: 2 breaking, 5 warning, 109 info - **2026-09-12** `e85c0a2a3253`: 5 info - **2026-08-26** `9e289a76248e`: 1 info ## Changes - **2026-10-17** `0e9a6f94eff0`: 3 info - added the new optional request property `bcc_emails` - added the new optional request property `cc_emails` - added the new optional request property `to_emails` - **2026-10-12** `40bf3229d58f`: 1 breaking, 7 info - the `data` response's property type changed from no type to `object` for status `200` - removed `#/components/schemas/CreateIssueDraftReplyResponseData` 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/status` to the response with the `200` status - added the required property `data/updated_at` to the response with the `200` status - added the required property `data/user_id` to the response with the `200` status - **2026-10-11** `dfb481067e5a`: 2 breaking, 5 warning, 109 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/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/status` from the response with the `200` status - removed the optional property `data/updated_at` from the response with the `200` status - removed the optional property `data/user_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/CreateIssueDraftReplyResponseData` 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 `409` - 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 `409` - 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 `409` - 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 `409` - 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 `409` - 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 `409` - …76 more - **2026-09-12** `e85c0a2a3253`: 5 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 `409` status - added the optional property `code` to the response with the `500` status - **2026-08-26** `9e289a76248e`: 1 info - endpoint added --- [Operation](https://skmtc.dev/usepylon/apis/pylon-api/docs/issues/:id/draft-reply/post.md) - [API](https://skmtc.dev/usepylon/apis/pylon-api.md) - [Page](https://skmtc.dev/usepylon/apis/pylon-api/changes/issues/:id/draft-reply/post)