Skip to content

Get a workflow pin ​

GET/api/v2/workspaces/{slug}/work-item-types/{type_id}/governance/pins/{pk}/

Retrieve one pin by id. A pin names the project, the work item type, and the catalog workflow the workspace fixed for that pair. See Pins.

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.

type_id:requiredstring (uuid)

The work item type the pin belongs to. A pin on a different type returns 404.

pk:requiredstring (uuid)

The id of the pin.

Response shaping ​

fields:optionalstring

Comma-separated list of fields to return. Unrequested keys are omitted from the response, not returned as null, so absent means "not requested" and null means "actually null". id always comes back whether or not you name it.

Pass all for every requestable field. An unknown name is a 400 that lists the valid set and suggests the closest match, so a typo can't silently cost you the saving.

Requestable here: created_at, id, project_id, updated_at, work_item_type_id, workflow_id.

See Sparse fields.

Scopes ​

workspaces.workflows:read

Errors ​

StatusCodeCause
401unauthorizedMissing or invalid credentials.
402payment_requiredWorkspace governance isn't on your plan.
403forbiddenYour role or token scope can't view workspace workflows.
404not_foundNo such work item type or pin in this workspace.
406not_acceptableThe Accept header asks for a representation the API can't produce.
429rate_limitedThrottled. Honor the Retry-After header before retrying.
Get a workflow pin
bash
curl -X GET \
  "https://api.plane.so/api/v2/workspaces/my-team/work-item-types/d1e7a4c9-2b58-4f36-9a0e-7c3b5d81f240/governance/pins/0b6d3f92-7e15-4a48-9c27-5f8e1a4d6b30/" \
  -H "X-Api-Key: $PLANE_API_KEY"
Response200
json
{
  "id": "0b6d3f92-7e15-4a48-9c27-5f8e1a4d6b30",
  "project_id": "4af68566-94a4-4eb3-94aa-50dc9427067b",
  "workflow_id": "e6b2d9f1-48a7-4c3e-9f50-1d7a8c2b6e93",
  "work_item_type_id": "d1e7a4c9-2b58-4f36-9a0e-7c3b5d81f240",
  "created_at": "2026-01-14T09:22:41.478363Z",
  "updated_at": "2026-01-14T09:22:41.478363Z"
}
Response404
json
{
  "type": "not_found",
  "code": "not_found",
  "detail": "The requested resource was not found."
}