--- title: "Changes to Create a new route redirect" method: POST path: "/knowledge-bases/{id}/route-redirects" --- # Changes to Create a new route redirect `POST /knowledge-bases/{id}/route-redirects` > Every recorded change to this operation, newest first. ## Timeline Changed in 4 of 63 revisions. - **2026-10-12** `40bf3229d58f`: 1 info - **2026-10-11** `dfb481067e5a`: 93 info - **2026-09-12** `e85c0a2a3253`: 4 info - **2026-08-28** `fe3adb90ea45`: 1 info ## Changes - **2026-10-12** `40bf3229d58f`: 1 info - the response property `data` became required for the status `200` - **2026-10-11** `dfb481067e5a`: 93 info - added the non-success response with the status `401` - added the non-success response with the status `409` - 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/from_path` became required for the status `200` - the response property `data/id` became required for the status `200` - the response property `data/object_id` became required for the status `200` - the response property `data/object_type` 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` - removed the `invalid_authorization_header` enum value from the `code` response property for the response status `500` - removed the `invalid_oauth_token` enum value from the `code` response property for the response status `400` - removed the `invalid_oauth_token` enum value from the `code` response property for the response status `403` - removed the `invalid_oauth_token` enum value from the `code` response property for the response status `404` - …53 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` --- [Operation](https://skmtc.dev/usepylon/apis/pylon-api/docs/knowledge-bases/:id/route-redirects/post.md) - [API](https://skmtc.dev/usepylon/apis/pylon-api.md) - [Page](https://skmtc.dev/usepylon/apis/pylon-api/changes/knowledge-bases/:id/route-redirects/post)