List workflow statuses

GEThttps://<your-url>/api/v2/workflow-statuses

MCP id workflow-statuses.indexAlso on this path: POST Create a workflow status

Returns the organisation's workflow statuses (the board columns work items sit in) in workflow order, with the id as the tiebreaker.

Token scope: api:read:workflows
Without it: 403 insufficient-token-scope.
Permission: workflows::read
Without it: 403 insufficient-permission.
Feature: Needs the sprints feature on your organisation.
Without it: 404 endpoint-not-found.
Rate cost: 1 unit, read bucket. view=detail makes it 3. Adds: each include +1, q +2.
Also: If-None-Match answers 304 when nothing changed. Cacheable: private, max-age=60. Unknown query parameters are refused, never ignored.

Both are checked, scope first. A token never does more than its user. How access is checked

Request

Example: One workflow's open columns, with the workflow expanded

curl -G \
  'https://<your-url>/api/v2/workflow-statuses' \
  --data-urlencode 'filter[workflow_id]=4' \
  --data-urlencode 'filter[is_resolution]=false' \
  --data-urlencode 'include=workflow' \
  -H 'Authorization: Bearer <token>' \
  -H 'Accept: application/json'

const response = await fetch('https://<your-url>/api/v2/workflow-statuses?filter[workflow_id]=4&filter[is_resolution]=false&include=workflow', {
  method: 'GET',
  headers: {
    'Authorization': 'Bearer <token>',
    'Accept': 'application/json',
  },
});

use Illuminate\Support\Facades\Http;

$response = Http::withToken('<token>')
    ->acceptJson()
    ->get('https://<your-url>/api/v2/workflow-statuses?filter[workflow_id]=4&filter[is_resolution]=false&include=workflow');

import requests
response = requests.request(
    'GET',
    'https://<your-url>/api/v2/workflow-statuses?filter[workflow_id]=4&filter[is_resolution]=false&include=workflow',
    headers={'Authorization': 'Bearer <token>', 'Accept': 'application/json'},
)

Response

The shape of the response, with sample values.

{
  "data": [
    {
      "id": 1,
      "workflow_id": 4,
      "name": "Done",
      "color": "#22c55e",
      "is_resolution": true,
      "order": 1,
      "created_at": "2026-03-04T09:15:00Z",
      "updated_at": "2026-03-04T09:15:00Z",
      "workflow": {
        "id": 1
      },
      "links": {
        "…": "1 field of WorkflowStatusLinks"
      }
    }
  ],
  "meta": {
    "page": {
      "per_page": 1,
      "next_cursor": "…",
      "prev_cursor": "…",
      "total": 1,
      "current_page": 1,
      "last_page": 1
    }
  },
  "links": {
    "self": "https://<your-url>/api/v2/work-items/1",
    "next": "https://<your-url>/api/v2/work-items/1",
    "prev": "https://<your-url>/api/v2/work-items/1"
  }
}

Statuses created through this API are created at position 0, so they tie with each other and sort by id. There is no nested path for one workflow's statuses: scope the collection with filter[workflow_id] instead, which is the URL a workflow's links.statuses points at. Available only while the Sprints feature is enabled.

Query parameters

Unknown parameters are refused with 400, naming the parameter.

16 parameters in 6 groups

Views

viewstring

Which field set to render.

summarydefaultdetail

Pagination

per_pageinteger1 to 100

Rows per page. At most 25 when include names a to-many relation; a larger value is 400 invalid-query-parameter.

Default: 25

cursorstring

Opaque keyset cursor from a previous page's links.next. Never construct one by hand.

pageinteger1 to 1000

Opt in to page-number paging: 1-based, at most 1000. Omit it, the default, to page by opaque cursor, which is what links.next hands you. Cannot be combined with cursor. Published only on collections that count their rows on every request. This collection's default sort is a display position that changes whenever someone drags the list into a new order in plnnrly, so a page number can skip or repeat a row if the list is reordered between two page requests. These collections rarely exceed one page; for a stable walk, send sort=id and follow links.next without page.

Filters

=: equals
[in]: any of a comma-separated list
[gte][lt]: at least, less than

filter[created_at]timestamp (YYYY-MM-DDThh:mm:ssZ)=[gte][lt]

Creation timestamp. Pair with sort=id for a stable full export.

filter[is_resolution]boolean

Whether reaching the status resolves the work item.

filter[updated_at]timestamp (YYYY-MM-DDThh:mm:ssZ)=[gte][lt]

Last-write timestamp. Use for incremental sync.

filter[workflow_id]integer=[in]

Workflow the status belongs to. This is how you list one workflow's statuses: there is no nested path for them.

A comma-separated list of at most 100 values.

Search

qstring

Free-text search over name. At most one substring match per request: q together with a contains filter is 400 invalid-query-parameter.

Sorting

sortstring

Up to three keys, comma-separated, each optionally prefixed with - for descending.

Default: order

Key	Sorts by
`order`	Position within the workflow, left to right on the board.
`name`	Status name, A→Z.
`id`	Id, ascending. An id never changes, so use this for a stable full export.
`updated_at`	Last-write timestamp; pair with the id tiebreaker for sync.

Prefix a key with - for descending.

Includes

includestring

Comma-separated names to inline, at most five.

Path	Adds	Cost
`workflow`	Workflow this status belongs to, with its name.	+1

Request headers

X-Request-Idstringpattern

A correlation id of your own. It is recorded in our logs next to the server's request id but never returned: the response header always carries the server's id. A value that does not match the pattern is discarded silently, never rejected.

If-None-Matchstring

The ETag a read is conditional on. A match is answered 304 with no body.

Response 200

Returns a page of WorkflowStatusList rows.

dataarray of WorkflowStatusList

The rows, each a WorkflowStatusList.

meta.pagePage

per_page, next_cursor, prev_cursor, total, current_page, last_page.

linksPageLinks

self, next, prev.

Each row is a WorkflowStatusList: 10 fields.

Headers

ETag: A weak validator (W/"…") of the rendered page.
RateLimit: The IETF httpapi-ratelimit-headers form of your remaining allowance on the tightest bucket this request touched.
RateLimit-Policy: The ceiling and window of that bucket, as <limit>;w=<seconds>.
X-Request-Id: The server-generated ULID correlating this response with our logs.

Every response also carries Cache-Control, Vary, X-Content-Type-Options, X-Plnnrly-Api-Version, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset. Headers and versioning