---
title: "Archive issue(s) by issue ID/key"
method: PUT
path: "/rest/api/3/issue/archive"
tags: ["Issues"]
---

# Archive issue(s) by issue ID/key

`PUT /rest/api/3/issue/archive`

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

**Note that:**

 *  you can't archive subtasks directly, only through their parent issues
 *  you can only archive 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 archive in the request. The return message will include the count of archived issues and subtasks, as well as error details for issues which failed to get archived.

- 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 can be archived. Possible reasons: * the issues weren't found * the issues are subtasks * the issues belong to unlicensed projects * the issues belong to archived projects
- `401` — Returned if no issues were archived because the provided authentication credentials are either missing or invalid.
- `403` — Returned if no issues were archived because the user lacks the required Jira admin or site admin permissions.
- `412` — Returned if one or more issues were successfully archived, 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)