--- title: "Changes to Create a training data configuration" method: POST path: "/training-data" --- # Changes to Create a training data configuration `POST /training-data` > Every recorded change to this operation, newest first. ## Timeline Changed in 5 of 63 revisions. - **2026-10-12** `40bf3229d58f`: 1 info - **2026-10-11** `dfb481067e5a`: 84 info - **2026-09-12** `e85c0a2a3253`: 3 info - **2026-08-28** `fe3adb90ea45`: 1 info - **2026-08-14** `ad855d921ee9`: 1 breaking, 3 warning, 4 info ## Changes - **2026-10-12** `40bf3229d58f`: 1 info - the response property `data` became required for the status `200` - **2026-10-11** `dfb481067e5a`: 84 info - 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/documents/items/file_name` became required for the status `200` - the response property `data/documents/items/file_size` became required for the status `200` - the response property `data/documents/items/file_type` became required for the status `200` - the response property `data/documents/items/id` became required for the status `200` - the response property `data/documents/items/s3_key` became required for the status `200` - the response property `data/exclude_from_kb_search` became required for the status `200` - the response property `data/id` became required for the status `200` - the response property `data/name` became required for the status `200` - the response property `data/scrape_status/pages_scraped` became required for the status `200` - the response property `data/scrape_status/status` became required for the status `200` - the response property `data/scrape_status/total_pages` became required for the status `200` - the response property `data/type` became required for the status `200` - the response property `data/updated_at` became required for the status `200` - the response property `data/visibility` 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 `500` - removed the `ai_agent_only` enum value from the `data/visibility` response property for the response status `200` - 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 `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 `500` - removed the `everyone` enum value from the `data/visibility` response property for the response status `200` - 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 `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 `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 `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` - …44 more - **2026-09-12** `e85c0a2a3253`: 3 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 `500` status - **2026-08-28** `fe3adb90ea45`: 1 info - added the non-success response with the status `403` - **2026-08-14** `ad855d921ee9`: 1 breaking, 3 warning, 4 info - request property `visibility` was restricted to a list of enum values - added the new `ai_agent_only` enum value to the `data/visibility` response property for the response status `200` - added the new `everyone` enum value to the `data/visibility` response property for the response status `200` - added the new `user_only` enum value to the `data/visibility` response property for the response status `200` - the `visibility` request property default value `everyone` was added - added the new `ai_agent_only` enum value to the request property `visibility` - added the new `everyone` enum value to the request property `visibility` - added the new `user_only` enum value to the request property `visibility` --- [Operation](https://skmtc.dev/usepylon/apis/pylon-api/docs/training-data/post.md) - [API](https://skmtc.dev/usepylon/apis/pylon-api.md) - [Page](https://skmtc.dev/usepylon/apis/pylon-api/changes/training-data/post)