--- title: "Changes to Migration only: Import a project" method: POST path: "/import/projects" --- # Changes to Migration only: Import a project `POST /import/projects` > Every recorded change to this operation, newest first. ## Timeline Changed in 7 of 63 revisions. - **2026-10-27** `554844ef05a1`: 1 info - **2026-10-12** `40bf3229d58f`: 1 info - **2026-10-11** `dfb481067e5a`: 6 breaking, 100 info - **2026-09-12** `e85c0a2a3253`: 4 info - **2026-09-05** `9f3f03fda615`: 2 info - **2026-08-28** `fe3adb90ea45`: 1 info - **2026-08-22** `d4db007b26b2`: 1 info ## Changes - **2026-10-27** `554844ef05a1`: 1 info - added the required property `data/ai_instructions` 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`: 6 breaking, 100 info - the `created_at` request property format changed from no format to `date-time` - the `end_date` request property format changed from no format to `date-time` - the `start_date` request property format changed from no format to `date-time` - the `updated_at` request property format changed from no format to `date-time` - the response property `data/account/external_ids` became nullable for the status `200` - the response property `data/custom_fields` 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/account/id` became required for the status `200` - the response property `data/created_at` became required for the status `200` - the response property `data/customer_portal_visible` became required for the status `200` - the response property `data/id` became required for the status `200` - the response property `data/is_archived` became required for the status `200` - the response property `data/name` became required for the status `200` - the response property `data/progress` became required for the status `200` - the response property `data/project_template/id` became required for the status `200` - the response property `data/status` 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 `completed` enum value from the `data/status` 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 `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 `in_progress` enum value from the `data/status` 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 `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` - …66 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-09-05** `9f3f03fda615`: 2 info - added the optional property `data/progress` to the response with the `200` status - added the optional property `data/status` to the response with the `200` status - **2026-08-28** `fe3adb90ea45`: 1 info - added the non-success response with the status `403` - **2026-08-22** `d4db007b26b2`: 1 info - endpoint added --- [Operation](https://skmtc.dev/usepylon/apis/pylon-api/docs/import/projects/post.md) - [API](https://skmtc.dev/usepylon/apis/pylon-api.md) - [Page](https://skmtc.dev/usepylon/apis/pylon-api/changes/import/projects/post)