Unarchive a work item

POST/api/v2/workspaces/{slug}/projects/{project_id}/work-items/{pk}/unarchive/

Restore an archived work item: clear archived_at and put it back into the active set, where it shows up in lists and plain detail reads again.

This is a bodyless POST — send no JSON at all. The response is the full work item in its usual read shape with archived_at back to null.

Unlike most detail routes, this one deliberately looks past the archive filter to find the work item — that is the whole point. It also means the call is safe to repeat: unarchiving a work item that isn't archived succeeds and changes nothing.

Path Parameters

slug:requiredstring

The workspace slug. It appears in your Plane URLs — in https://app.plane.so/my-team/projects/, the slug is my-team.

project_id:requiredstring (uuid)

The project the work item belongs to.

pk:requiredstring (uuid)

The work item's UUID. This lookup is UUID-only — a PROJ-142 identifier here returns 404.

Body Parameters

None. The endpoint takes no request body; anything you send is ignored.

Safe to retry

Unarchive resolves archived and active work items alike, so a repeat call is a no-op that returns 200 with archived_at: null. Archive is the asymmetric one — see Archive a work item.

Scopes

projects.work_items:write

Errors

Status	Code	Cause
400	validation_error	The request could not be processed — for example a pk that isn't a valid UUID.
401	unauthorized	Missing or invalid credentials.
403	forbidden	Your role or token scope can't archive or unarchive this work item.
404	resource_not_found	No such work item, or it's outside your project or tenant.
409	conflict	The write collides with a protected-resource constraint.
429	rate_limited	Throttled. Honor the Retry-After header before retrying.

Unarchive a work item

curl -X POST \
  "https://api.plane.so/api/v2/workspaces/my-team/projects/4af68566-94a4-4eb3-94aa-50dc9427067b/work-items/8f4c2b1e-0d3a-4f7b-9c21-6e5a8b7d4f13/unarchive/" \
  -H "X-Api-Key: $PLANE_API_KEY"

import requests

response = requests.post(
    "https://api.plane.so/api/v2/workspaces/my-team/projects/4af68566-94a4-4eb3-94aa-50dc9427067b"
    "/work-items/8f4c2b1e-0d3a-4f7b-9c21-6e5a8b7d4f13/unarchive/",
    headers={"X-Api-Key": "your-api-key"},
)
print(response.json()["archived_at"])  # None

const response = await fetch(
  "https://api.plane.so/api/v2/workspaces/my-team/projects/4af68566-94a4-4eb3-94aa-50dc9427067b" +
    "/work-items/8f4c2b1e-0d3a-4f7b-9c21-6e5a8b7d4f13/unarchive/",
  {
    method: "POST",
    headers: { "X-Api-Key": "your-api-key" },
  }
);
const data = await response.json();

Response200

{
  "id": "8f4c2b1e-0d3a-4f7b-9c21-6e5a8b7d4f13",
  "name": "Fix login redirect loop",
  "identifier": "PROJ-142",
  "sequence_id": 142,
  "priority": "high",
  "state_id": "f960d3c2-8524-4a41-b8eb-055ce4be2a7f",
  "type_id": "2d9d1a97-5c6f-4a1e-9d5b-8c2f7e30b6a4",
  "assignee_ids": ["16c61a3a-512a-48ac-b0be-b6b46fe6f430"],
  "label_ids": ["c1b8f3d6-9a44-4e12-8f7a-2b6d5c9e1a03"],
  "parent_id": null,
  "start_date": "2026-01-12",
  "target_date": "2026-01-20",
  "is_draft": false,
  "archived_at": null,
  "created_at": "2026-01-14T09:22:41.478363Z",
  "created_by_id": "16c61a3a-512a-48ac-b0be-b6b46fe6f430",
  "custom_fields": null
}

Response404

{
  "type": "https://api.plane.so/errors/resource_not_found",
  "title": "Not Found",
  "status": 404,
  "code": "resource_not_found",
  "detail": "The requested resource was not found."
}

What comes back, and what doesn't

The response is the work item's standard read shape with archived_at cleared. custom_fields is null here — the archive verbs return the work item, not its custom property values. Fetch the work item afterwards if you need them.

Nothing else is restored or changed, because nothing else was touched when the work item was archived: state, assignees, labels, dates, comments, and relations all survived the archive untouched.

Finding archived work items to restore

Archived work items are excluded from List work items and from plain detail reads, so the API gives you nothing to browse them with. Record the id when you archive — the archive response returns it — or pick the work item out of the Plane app's archive view, then unarchive it by UUID. This route is the one place an archived work item still resolves.