Delete a workspace work item property

DELETE/api/v2/workspaces/{slug}/work-item-properties/{pk}/

Remove a property from the workspace catalog. The delete is soft and the response is 204 with an empty body.

This is the wide blast radius option: the property leaves every project and work item type it reached, unlike detaching it from a single type, which only affects that one type.

Retire before you delete

If the property has been collecting values, PATCH it with is_active: false first. The definition stays addressable while you migrate, and you can reverse the decision with a single field. Deleting is the move for a property created by mistake.

Wrong mode is a 409, not a 404

If the workspace manages work item types at the project level, this route returns 409 with the code work_item_types_managed_at_project. Delete the property on the project-level resource instead. See Work item type modes.

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.

pk:requiredstring (uuid)

The property's id.

Scopes

workspaces.work_item_properties:write

Errors

Status	Code	Cause
400	validation_error	The request failed validation — most often a pk that isn't a valid UUID.
401	unauthorized	Missing or invalid credentials.
403	forbidden	Your role or token scope can't write workspace work item properties.
404	resource_not_found	No such workspace or property, or it's outside your tenant.
409	work_item_types_managed_at_project	This workspace manages work item types at the project level.
429	rate_limited	Throttled. Honor the Retry-After header before retrying.

Delete a workspace property

curl -X DELETE \
  "https://api.plane.so/api/v2/workspaces/my-team/work-item-properties/a7e3f1d0-5c92-4b68-8f31-2d4a6b9e0c15/" \
  -H "X-Api-Key: $PLANE_API_KEY"

import requests

response = requests.delete(
    "https://api.plane.so/api/v2/workspaces/my-team/work-item-properties/a7e3f1d0-5c92-4b68-8f31-2d4a6b9e0c15/",
    headers={"X-Api-Key": "your-api-key"},
)
print(response.status_code)

const response = await fetch(
  "https://api.plane.so/api/v2/workspaces/my-team/work-item-properties/a7e3f1d0-5c92-4b68-8f31-2d4a6b9e0c15/",
  {
    method: "DELETE",
    headers: {
      "X-Api-Key": "your-api-key",
    },
  }
);
console.log(response.status);

Response204

No content

Response409

{
  "type": "https://api.plane.so/errors/work-item-types-managed-at-project",
  "title": "Conflict",
  "status": 409,
  "code": "work_item_types_managed_at_project",
  "detail": "This workspace manages work item types at the project level. Use the project-level endpoint instead."
}

Deleting the property takes its scoping with it

A property's contexts and options are mounted underneath it. Once the property is gone, those sub-resources are no longer addressable — GETs under the deleted property_id return 404 resource_not_found.