---
title: "Changes to Get people"
method: GET
path: "/api/v2/people"
---

# Changes to Get people

`GET /api/v2/people`

> Every recorded change to this operation, newest first.

## Timeline

Changed in 5 of 49 revisions.

- **2026-11-03** `e7bdfdf6cba3`: 2 info
- **2026-11-02** `fa3060fd0144`: 7 info
- **2026-10-27** `f11a8740641a`: 41 breaking, 1 warning, 114 info
- **2026-09-08** `8f5c7905990c`: 5 breaking
- **2026-08-27** `bbf5057edf0d`: 3 breaking

## Changes

- **2026-11-03** `e7bdfdf6cba3`: 2 info
  - added the optional property `data/items/attributes/ai_assistant_avatar_url` to the response with the `200` status
  - added the optional property `data/items/attributes/ai_assistant_name` to the response with the `200` status
- **2026-11-02** `fa3060fd0144`: 7 info
  - added the non-success response with the status `400`
  - added the non-success response with the status `401`
  - added the non-success response with the status `403`
  - added the non-success response with the status `408`
  - added the non-success response with the status `423`
  - added the non-success response with the status `429`
  - added the non-success response with the status `500`
- **2026-10-27** `f11a8740641a`: 41 breaking, 1 warning, 114 info
  - for the `query` request parameter `filter`, the type of property `oneOf[subschema #1: Filter person -> subschema #2: Filter person]/person_type/oneOf[subschema #1: Operation]/contains` was specialized from `string` to `integer`
  - for the `query` request parameter `filter`, the type of property `oneOf[subschema #1: Filter person -> subschema #2: Filter person]/person_type/oneOf[subschema #1: Operation]/eq` was specialized from `string` to `integer`
  - for the `query` request parameter `filter`, the type of property `oneOf[subschema #1: Filter person -> subschema #2: Filter person]/person_type/oneOf[subschema #1: Operation]/not_contain` was specialized from `string` to `integer`
  - for the `query` request parameter `filter`, the type of property `oneOf[subschema #1: Filter person -> subschema #2: Filter person]/person_type/oneOf[subschema #1: Operation]/not_eq` was specialized from `string` to `integer`
  - for the `query` request parameter `filter`, the type of property `oneOf[subschema #1: Filter person -> subschema #2: Filter person]/person_type/oneOf[subschema #2: Person Type]/` was specialized from `string` to `integer`
  - the `data/items/attributes/archived_at` response's property type changed from `string` to no type, and format from `date-time` to no format for status `200`
  - the `data/items/attributes/availabilities` response's property type changed from no type to `string` for status `200`
  - the `data/items/attributes/avatar_url` response's property type changed from `string` to no type for status `200`
  - the `data/items/attributes/champion` response's property type changed from no type to `boolean` for status `200`
  - the `data/items/attributes/color_id` response's property type changed from `integer` to no type for status `200`
  - the `data/items/attributes/contact` response's property type changed from `object` to no type for status `200`
  - the `data/items/attributes/custom_fields` response's property type changed from `object` to no type for status `200`
  - the `data/items/attributes/deactivated_at` response's property type changed from `string` to no type, and format from `date-time` to no format for status `200`
  - the `data/items/attributes/email` response's property type changed from `string` to no type for status `200`
  - the `data/items/attributes/external_id` response's property type changed from `string` to no type for status `200`
  - the `data/items/attributes/first_name` response's property type changed from `string` to no type for status `200`
  - the `data/items/attributes/hrm_type_id` response's property type changed from `integer` to no type for status `200`
  - the `data/items/attributes/invited_at` response's property type changed from `string` to no type, and format from `date-time` to no format for status `200`
  - the `data/items/attributes/is_user` response's property type changed from no type to `boolean` for status `200`
  - the `data/items/attributes/joined_at` response's property type changed from `string` to no type, and format from `date-time` to no format for status `200`
  - the `data/items/attributes/last_activity_at` response's property type changed from `string` to no type, and format from `date-time` to no format for status `200`
  - the `data/items/attributes/last_name` response's property type changed from `string` to no type for status `200`
  - the `data/items/attributes/last_seen_at` response's property type changed from `string` to no type, and format from `date-time` to no format for status `200`
  - the `data/items/attributes/nickname` response's property type changed from `string` to no type for status `200`
  - the `data/items/attributes/offboarding_id` response's property type changed from `integer` to no type for status `200`
  - the `data/items/attributes/original_avatar_url` response's property type changed from `string` to no type for status `200`
  - the `data/items/attributes/role_id` response's property type changed from `integer` to no type for status `200`
  - the `data/items/attributes/status_emoji` response's property type changed from `string` to no type for status `200`
  - the `data/items/attributes/status_expires_at` response's property type changed from `string` to no type, and format from `date-time` to no format for status `200`
  - the `data/items/attributes/status_text` response's property type changed from `string` to no type for status `200`
  - the `data/items/attributes/tag_list` response's property type changed from `string` to `array` for status `200`
  - the `data/items/attributes/time_tracking_policy_id` response's property type changed from `integer` to no type for status `200`
  - the `data/items/attributes/time_unlocked` response's property type changed from `boolean` to no type for status `200`
  - the `data/items/attributes/time_unlocked_end_date` response's property type changed from `string` to no type, and format from `date` to no format for status `200`
  - the `data/items/attributes/time_unlocked_interval` response's property type changed from `integer` to no type for status `200`
  - the `data/items/attributes/time_unlocked_on` response's property type changed from `string` to no type, and format from `date` to no format for status `200`
  - the `data/items/attributes/time_unlocked_period_id` response's property type changed from `integer` to no type for status `200`
  - the `data/items/attributes/time_unlocked_start_date` response's property type changed from `string` to no type, and format from `date` to no format for status `200`
  - the `data/items/attributes/title` response's property type changed from `string` to no type for status `200`
  - the `data/items/attributes/two_factor_auth` response's property type changed from `boolean` to no type for status `200`
  - …116 more
  - …this revision’s changelog is incomplete
- **2026-09-08** `8f5c7905990c`: 5 breaking
  - for the `query` request parameter `filter`, the type of property `oneOf[subschema #1: Filter person]/job_role_id/oneOf[#/components/schemas/job_role_id -> subschema #1: Job Role]/` was specialized from no type to `integer`
  - for the `query` request parameter `filter`, the type of property `oneOf[subschema #1: Filter person]/job_role_id/oneOf[subschema #1: Operation -> subschema #2: Operation]/contains` was specialized from no type to `integer`
  - for the `query` request parameter `filter`, the type of property `oneOf[subschema #1: Filter person]/job_role_id/oneOf[subschema #1: Operation -> subschema #2: Operation]/eq` was specialized from no type to `integer`
  - for the `query` request parameter `filter`, the type of property `oneOf[subschema #1: Filter person]/job_role_id/oneOf[subschema #1: Operation -> subschema #2: Operation]/not_contain` was specialized from no type to `integer`
  - for the `query` request parameter `filter`, the type of property `oneOf[subschema #1: Filter person]/job_role_id/oneOf[subschema #1: Operation -> subschema #2: Operation]/not_eq` was specialized from no type to `integer`
- **2026-08-27** `bbf5057edf0d`: 3 breaking
  - for the `query` request parameter `filter`, the type of property `oneOf[subschema #2: Filter person -> subschema #1: Filter person]/shared_seat/oneOf[#/components/schemas/shared_seat -> subschema #2: Shared Seat]/` was specialized from no type to `boolean`
  - for the `query` request parameter `filter`, the type of property `oneOf[subschema #2: Filter person -> subschema #1: Filter person]/shared_seat/oneOf[subschema #2: Operation -> subschema #1: Operation]/eq` was specialized from no type to `boolean`
  - for the `query` request parameter `filter`, the type of property `oneOf[subschema #2: Filter person -> subschema #1: Filter person]/shared_seat/oneOf[subschema #2: Operation -> subschema #1: Operation]/not_eq` was specialized from no type to `boolean`

---

[Operation](https://skmtc.dev/productive/apis/api-documentation/docs/api/v2/people/get.md) - [API](https://skmtc.dev/productive/apis/api-documentation.md) - [Page](https://skmtc.dev/productive/apis/api-documentation/changes/api/v2/people/get)
