---
title: "Unarchive issue(s) by issue keys/ID"
method: PUT
path: "/rest/api/3/issue/unarchive"
tags: ["Issues"]
---

# Unarchive issue(s) by issue keys/ID

`PUT /rest/api/3/issue/unarchive`

Enables admins to unarchive up to 1000 issues in a single request using issue ID/key, returning details of the issue(s) unarchived in the process and the errors encountered, if any.

**Note that:**

 *  you can't unarchive subtasks directly, only through their parent issues
 *  you can only unarchive issues from software, service management, and business projects

**[Permissions](#permissions) required:** Jira admin or site admin: [global permission](https://confluence.atlassian.com/x/x4dKLg)

**License required:** Premium or Enterprise

**Signed-in users only:** This API can't be accessed anonymously.

## Request body

- IssueArchivalSyncRequest — List of Issue Ids Or Keys that are to be archived or unarchived
  - `issueIdsOrKeys` string[]

## Response `200`

Returned if there is at least one valid issue to unarchive in the request. It will return the count of unarchived issues, which also includes the count of the subtasks unarchived, and it will show the detailed errors for those issues which are not unarchived.

- IssueArchivalSyncResponse — Number of archived/unarchived issues and list of errors that occurred during the action, if any.
  - `errors` Errors
    - `issueIsSubtask` Error
      - `count` integer
      - `issueIdsOrKeys` string[]
      - `message` string
    - `issuesInArchivedProjects` Error
      - `count` integer
      - `issueIdsOrKeys` string[]
      - `message` string
    - `issuesInUnlicensedProjects` Error
      - `count` integer
      - `issueIdsOrKeys` string[]
      - `message` string
    - `issuesNotFound` Error
      - `count` integer
      - `issueIdsOrKeys` string[]
      - `message` string
    - `userDoesNotHavePermission` Error
      - `count` integer
      - `issueIdsOrKeys` string[]
      - `message` string
  - `numberOfIssuesUpdated` integer

## Other responses

- `400` — Returned if none of the issues in the request are eligible to be unarchived. Possible reasons: * the issues weren't found * the issues are subtasks * the issues belong to archived projects
- `401` — Returned if no issues were unarchived because the provided authentication credentials are either missing or invalid.
- `403` — Returned if no issues were unarchived because the user lacks the required Jira admin or site admin permissions.
- `412` — Returned if one or more issues were successfully unarchived, but the operation was incomplete because the number of issue IDs or keys provided exceeds 1000.

---

[API](https://skmtc.net/atlassian/apis/the-jira-cloud-platform-rest-api-2.md) · [All operations](https://skmtc.net/atlassian/apis/the-jira-cloud-platform-rest-api-2/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/atlassian/the-jira-cloud-platform-rest-api-2/versions/ec7f275dfee5/schema)