--- title: "Changes to Create a new team" method: POST path: "/teams" --- # Changes to Create a new team `POST /teams` > Every recorded change to this operation, newest first. ## Timeline Changed in 8 of 63 revisions. - **2026-10-16** `03732ec8280a`: 2 info - **2026-10-12** `40bf3229d58f`: 1 info - **2026-10-11** `dfb481067e5a`: 2 breaking, 96 info - **2026-09-12** `e85c0a2a3253`: 4 info - **2026-09-11** `de90acc15255`: 2 warning - **2026-09-02** `cef2ab0dd800`: 4 info - **2026-08-28** `fe3adb90ea45`: 1 info - **2026-08-18** `b387b041ea8e`: 1 breaking ## Changes - **2026-10-16** `03732ec8280a`: 2 info - added the new optional request property `assignment_configuration/assignable_user_statuses` - added the optional property `data/assignment_configuration/assignable_user_statuses` 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`: 2 breaking, 96 info - the response property `data/schedule/blocks` became nullable for the status `200` - the response property `data/users` 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/assignment_configuration/assignment_method` became required for the status `200` - the response property `data/assignment_configuration/only_assign_if_user_active` became required for the status `200` - the response property `data/assignment_configuration/override_existing_assignee` 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/schedule/blocks/items/recurrence` became required for the status `200` - the response property `data/schedule/id` became required for the status `200` - the response property `data/schedule/timezone` became required for the status `200` - the response property `data/users/items/id` 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` - …58 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-11** `de90acc15255`: 2 warning - removed the request property `schedule/support_hours_id` - removed the optional property `data/schedule/support_hours_id` from the response with the `200` status - **2026-09-02** `cef2ab0dd800`: 4 info - added the new optional request property `assignment_configuration` - added the new optional request property `schedule` - added the optional property `data/assignment_configuration` to the response with the `200` status - added the optional property `data/schedule` to the response with the `200` status - **2026-08-28** `fe3adb90ea45`: 1 info - added the non-success response with the status `403` - **2026-08-18** `b387b041ea8e`: 1 breaking - the request property `name` became required --- [Operation](https://skmtc.dev/usepylon/apis/pylon-api/docs/teams/post.md) - [API](https://skmtc.dev/usepylon/apis/pylon-api.md) - [Page](https://skmtc.dev/usepylon/apis/pylon-api/changes/teams/post)