--- title: "Changes to Get a list of teams" method: GET path: "/teams" --- # Changes to Get a list of teams `GET /teams` > Every recorded change to this operation, newest first. ## Timeline Changed in 6 of 63 revisions. - **2026-10-16** `03732ec8280a`: 1 info - **2026-10-11** `dfb481067e5a`: 2 breaking, 97 info - **2026-09-12** `e85c0a2a3253`: 4 info - **2026-09-11** `de90acc15255`: 1 warning - **2026-09-02** `cef2ab0dd800`: 2 info - **2026-08-28** `fe3adb90ea45`: 1 info ## Changes - **2026-10-16** `03732ec8280a`: 1 info - added the optional property `data/items/assignment_configuration/assignable_user_statuses` to the response with the `200` status - **2026-10-11** `dfb481067e5a`: 2 breaking, 97 info - the response property `data/items/schedule/blocks` became nullable for the status `200` - the response property `data/items/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` became required for the status `200` - the response property `data/items/assignment_configuration/assignment_method` became required for the status `200` - the response property `data/items/assignment_configuration/only_assign_if_user_active` became required for the status `200` - the response property `data/items/assignment_configuration/override_existing_assignee` became required for the status `200` - the response property `data/items/id` became required for the status `200` - the response property `data/items/name` became required for the status `200` - the response property `data/items/schedule/blocks/items/recurrence` became required for the status `200` - the response property `data/items/schedule/id` became required for the status `200` - the response property `data/items/schedule/timezone` became required for the status `200` - the response property `data/items/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` - …59 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`: 1 warning - removed the optional property `data/items/schedule/support_hours_id` from the response with the `200` status - **2026-09-02** `cef2ab0dd800`: 2 info - added the optional property `data/items/assignment_configuration` to the response with the `200` status - added the optional property `data/items/schedule` to the response with the `200` 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/teams/get.md) - [API](https://skmtc.dev/usepylon/apis/pylon-api.md) - [Page](https://skmtc.dev/usepylon/apis/pylon-api/changes/teams/get)