---
title: "Changes to Restores a deleted item (answers the restored record in its own type; the schema shows the task case)"
method: PATCH
path: "/api/v2/deleted_items/{id}/restore"
---

# Changes to Restores a deleted item (answers the restored record in its own type; the schema shows the task case)

`PATCH /api/v2/deleted_items/{id}/restore`

> Every recorded change to this operation, newest first.

## Timeline

Changed in 4 of 49 revisions.

- **2026-11-03** `e7bdfdf6cba3`: 2 info
- **2026-11-02** `fa3060fd0144`: 3 warning, 9 info
- **2026-10-29** `2eb527b17709`: 1 breaking, 8 warning, 60 info
- **2026-10-27** `f11a8740641a`: 2 breaking, 1 warning, 16 info

## Changes

- **2026-11-03** `e7bdfdf6cba3`: 2 info
  - added the optional property `included/items/oneOf[subschema #3: Person]/attributes/ai_assistant_avatar_url` to the response with the `200` status
  - added the optional property `included/items/oneOf[subschema #3: Person]/attributes/ai_assistant_name` to the response with the `200` status
- **2026-11-02** `fa3060fd0144`: 3 warning, 9 info
  - added the new `bad_decimal_format` enum value to the `errors/items/code` response property for the response status `422`
  - added the new `non_finite_number` enum value to the `errors/items/code` response property for the response status `422`
  - added the new `null_bytes_in_params` enum value to the `errors/items/code` response property for the response status `422`
  - 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 `404`
  - added the non-success response with the status `406`
  - 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-29** `2eb527b17709`: 1 breaking, 8 warning, 60 info
  - added `#/components/schemas/_response_object_task, #/components/schemas/_response_object_project, #/components/schemas/_response_object_person, subschema #4: Other resource` to the `included/items/` response property `oneOf` list for the response status `200`
  - removed the optional property `data/attributes/deleter_id` from the response with the `200` status
  - removed the optional property `data/attributes/item_id` from the response with the `200` status
  - removed the optional property `data/attributes/item_type` from the response with the `200` status
  - removed the optional property `data/attributes/location` from the response with the `200` status
  - removed the optional property `data/attributes/name` from the response with the `200` status
  - removed the optional property `data/attributes/recovered_at` from the response with the `200` status
  - removed the optional property `data/relationships/deleter` from the response with the `200` status
  - added the new `tasks` enum value to the `data/type` response property for the response status `200`
  - added the optional property `data/attributes/billable_time` to the response with the `200` status
  - added the optional property `data/attributes/blocking_dependency_count` to the response with the `200` status
  - added the optional property `data/attributes/booked_time` to the response with the `200` status
  - added the optional property `data/attributes/bookings_count` to the response with the `200` status
  - added the optional property `data/attributes/closed` to the response with the `200` status
  - added the optional property `data/attributes/closed_at` to the response with the `200` status
  - added the optional property `data/attributes/creation_method_id` to the response with the `200` status
  - added the optional property `data/attributes/custom_fields` to the response with the `200` status
  - added the optional property `data/attributes/deleted_at` to the response with the `200` status
  - added the optional property `data/attributes/description` to the response with the `200` status
  - added the optional property `data/attributes/due_date` to the response with the `200` status
  - added the optional property `data/attributes/due_time` to the response with the `200` status
  - added the optional property `data/attributes/email_key` to the response with the `200` status
  - added the optional property `data/attributes/future_booked_time` to the response with the `200` status
  - added the optional property `data/attributes/initial_estimate` to the response with the `200` status
  - added the optional property `data/attributes/last_activity_at` to the response with the `200` status
  - added the optional property `data/attributes/linked_dependency_count` to the response with the `200` status
  - added the optional property `data/attributes/number` to the response with the `200` status
  - added the optional property `data/attributes/open_subtask_count` to the response with the `200` status
  - added the optional property `data/attributes/open_todo_count` to the response with the `200` status
  - added the optional property `data/attributes/placement` to the response with the `200` status
  - added the optional property `data/attributes/remaining_time` to the response with the `200` status
  - added the optional property `data/attributes/repeat_on_date` to the response with the `200` status
  - added the optional property `data/attributes/repeat_on_interval` to the response with the `200` status
  - added the optional property `data/attributes/repeat_on_monthday` to the response with the `200` status
  - added the optional property `data/attributes/repeat_on_weekday` to the response with the `200` status
  - added the optional property `data/attributes/repeat_origin_id` to the response with the `200` status
  - added the optional property `data/attributes/repeat_schedule_id` to the response with the `200` status
  - added the optional property `data/attributes/start_date` to the response with the `200` status
  - added the optional property `data/attributes/subtask_count` to the response with the `200` status
  - added the optional property `data/attributes/subtask_placement` to the response with the `200` status
  - …29 more
- **2026-10-27** `f11a8740641a`: 2 breaking, 1 warning, 16 info
  - the `data/attributes/location` response's property type changed from `string` to no type for status `200`
  - the `data/attributes/recovered_at` response's property type changed from `string` to no type, and format from `date-time` to no format for status `200`
  - deleted the `header` request parameter `X-Organization-Id`
  - added the new optional `query` request parameter `fields`
  - added the new optional `query` request parameter `include`
  - added the non-success response with the status `422`
  - added `#/components/schemas/_single_linkage_nullable` to the `data/relationships/deleter` response property `anyOf` list for the response status `200`
  - added `#/components/schemas/_single_linkage_nullable` to the `data/relationships/organization` response property `anyOf` list for the response status `200`
  - added `#/components/schemas/location, subschema #2` to the `data/attributes/location` response property `anyOf` list for the response status `200`
  - added `#/components/schemas/recovered_at, subschema #2` to the `data/attributes/recovered_at` response property `anyOf` list for the response status `200`
  - removed `subschema #1: Single data` from the `data/relationships/deleter` response property `anyOf` list for the response status `200`
  - removed `subschema #1: Single data` from the `data/relationships/organization` response property `anyOf` list for the response status `200`
  - the response property `data` became required for the status `200`
  - the response property `data/relationships/deleter/anyOf[subschema #2: Not included]/meta` became required for the status `200`
  - the response property `data/relationships/deleter/anyOf[subschema #2: Not included]/meta/included` became required for the status `200`
  - the response property `data/relationships/organization/anyOf[subschema #2: Not included]/meta` became required for the status `200`
  - the response property `data/relationships/organization/anyOf[subschema #2: Not included]/meta/included` became required for the status `200`
  - added the required property `data/id` to the response with the `200` status
  - added the required property `data/type` to the response with the `200` status
  - …this revision’s changelog is incomplete

---

[Operation](https://skmtc.dev/productive/apis/api-documentation/docs/api/v2/deleted_items/:id/restore/patch.md) - [API](https://skmtc.dev/productive/apis/api-documentation.md) - [Page](https://skmtc.dev/productive/apis/api-documentation/changes/api/v2/deleted_items/:id/restore/patch)
