---
title: "Changes to Get time reports"
method: GET
path: "/api/v2/reports/time_reports"
---

# Changes to Get time reports

`GET /api/v2/reports/time_reports`

> Every recorded change to this operation, newest first.

## Timeline

Changed in 4 of 49 revisions.

- **2026-11-02** `fa3060fd0144`: 7 info
- **2026-10-27** `f11a8740641a`: 28 breaking, 1 warning
- **2026-09-14** `c94f017bd3e5`: 5 warning
- **2026-09-08** `8f5c7905990c`: 5 breaking

## Changes

- **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`: 28 breaking, 1 warning
  - the `data/items/attributes/available_time` response's property type changed from `number` to no type for status `200`
  - the `data/items/attributes/billable_time` response's property type changed from `number` to no type for status `200`
  - the `data/items/attributes/billing_type` response's property type changed from `integer` to no type for status `200`
  - the `data/items/attributes/capacity` response's property type changed from `number` to no type for status `200`
  - the `data/items/attributes/client_time` response's property type changed from `number` to no type for status `200`
  - the `data/items/attributes/currency` response's property type changed from `string` to no type for status `200`
  - the `data/items/attributes/draft_scheduled_billable_time` response's property type changed from `number` to no type for status `200`
  - the `data/items/attributes/draft_scheduled_client_time` response's property type changed from `number` to no type for status `200`
  - the `data/items/attributes/draft_scheduled_internal_time` response's property type changed from `number` to no type for status `200`
  - the `data/items/attributes/draft_scheduled_time` response's property type changed from `number` to no type for status `200`
  - the `data/items/attributes/event_time` response's property type changed from `number` to no type for status `200`
  - the `data/items/attributes/holiday_time` response's property type changed from `number` to no type for status `200`
  - the `data/items/attributes/internal_time` response's property type changed from `number` to no type for status `200`
  - the `data/items/attributes/paid_event_time` response's property type changed from `number` to no type for status `200`
  - the `data/items/attributes/people_custom_fields` response's property type changed from `string` to `object` for status `200`
  - the `data/items/attributes/recognized_scheduled_time` response's property type changed from `number` to no type for status `200`
  - the `data/items/attributes/recognized_time` response's property type changed from `number` to no type for status `200`
  - the `data/items/attributes/scheduled_billable_time` response's property type changed from `number` to no type for status `200`
  - the `data/items/attributes/scheduled_client_time` response's property type changed from `number` to no type for status `200`
  - the `data/items/attributes/scheduled_event_time` response's property type changed from `number` to no type for status `200`
  - the `data/items/attributes/scheduled_internal_time` response's property type changed from `number` to no type for status `200`
  - the `data/items/attributes/scheduled_remote_work_time` response's property type changed from `number` to no type for status `200`
  - the `data/items/attributes/scheduled_time` response's property type changed from `number` to no type for status `200`
  - the `data/items/attributes/unapproved_time` response's property type changed from `number` to no type for status `200`
  - the `data/items/attributes/unpaid_event_time` response's property type changed from `number` to no type for status `200`
  - the `data/items/attributes/user_capacity` response's property type changed from `number` to no type for status `200`
  - the `data/items/attributes/worked_time` response's property type changed from `number` to no type for status `200`
  - the `data/items/attributes/workload` response's property type changed from `number` to no type for status `200`
  - deleted the `header` request parameter `X-Organization-Id`
  - …this revision’s changelog is incomplete
- **2026-09-14** `c94f017bd3e5`: 5 warning
  - for the `query` request parameter `filter`, the type of property `oneOf[subschema #2: Filter new time report]/role_type/oneOf[subschema #1: Role Type -> #/components/schemas/role_type]/` changed from `string` to no type
  - for the `query` request parameter `filter`, the type of property `oneOf[subschema #2: Filter new time report]/role_type/oneOf[subschema #2: Operation -> subschema #1: Operation]/contains` changed from `string` to no type
  - for the `query` request parameter `filter`, the type of property `oneOf[subschema #2: Filter new time report]/role_type/oneOf[subschema #2: Operation -> subschema #1: Operation]/eq` changed from `string` to no type
  - for the `query` request parameter `filter`, the type of property `oneOf[subschema #2: Filter new time report]/role_type/oneOf[subschema #2: Operation -> subschema #1: Operation]/not_contain` changed from `string` to no type
  - for the `query` request parameter `filter`, the type of property `oneOf[subschema #2: Filter new time report]/role_type/oneOf[subschema #2: Operation -> subschema #1: Operation]/not_eq` changed from `string` to no type
- **2026-09-08** `8f5c7905990c`: 5 breaking
  - for the `query` request parameter `filter`, the type of property `oneOf[subschema #1: Filter new time report]/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 new time report]/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 new time report]/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 new time report]/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 new time report]/job_role_id/oneOf[subschema #1: Operation -> subschema #2: Operation]/not_eq` was specialized from no type to `integer`

---

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