List a project's tasks

GEThttps://<your-url>/api/v2/projects/{project}/tasks

MCP id projects.tasks.indexAlso on this path: POST Create a task on a project

Returns the kanban tasks on one project, lowest board position first.

Token scope: api:read:kanban
Without it: 403 insufficient-token-scope.
Permission: kanban::manage_self
Without it: 403 insufficient-permission.
Rate cost: 1 unit, read bucket. view=detail makes it 3. Adds: with_total=1 +2, q +2.
Also: If-None-Match answers 304 when nothing changed. Never cached: private, no-store. 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: My open cards on one project, soonest due first

curl -G \
  'https://<your-url>/api/v2/projects/1/tasks' \
  --data-urlencode 'filter[is_finished]=false' \
  --data-urlencode 'sort=due_date,order_column' \
  -H 'Authorization: Bearer <token>' \
  -H 'Accept: application/json'

const response = await fetch('https://<your-url>/api/v2/projects/1/tasks?filter[is_finished]=false&sort=due_date%2Corder_column', {
  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/projects/1/tasks?filter[is_finished]=false&sort=due_date%2Corder_column');

import requests
response = requests.request(
    'GET',
    'https://<your-url>/api/v2/projects/1/tasks?filter[is_finished]=false&sort=due_date%2Corder_column',
    headers={'Authorization': 'Bearer <token>', 'Accept': 'application/json'},
)

Response

The shape of the response, with sample values.

{
  "data": [
    {
      "id": 1,
      "budget_id": 1,
      "user_id": 1,
      "team_id": 1,
      "due_date": "2026-09-15",
      "minutes": 240,
      "description": "Wire up the SSO callback",
      "comment": "…",
      "is_finished": false,
      "is_billable": false,
      "status": "on-hold",
      "order_column": 1
    }
  ],
  "meta": {
    "page": {
      "per_page": 1,
      "next_cursor": "…",
      "prev_cursor": "…",
      "total": 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"
  }
}

5 more fields, listed under Response

There is no organisation-wide collection of tasks (a kanban board is per-user), so this nested path is the only way to list them, and filter[project_id] / filter[customer_id] do not exist: the project is the path segment. Tasks are per-user, so filter[user_id] defaults to the authenticated user and naming another user requires kanban::manage_for_others; without that permission you also do not see the cards left unassigned in plnnrly. Listing additionally requires projects::read on the parent project: the declared kanban::manage_self is only part of the requirement. A trashed project answers 404 unless trashed=with is passed. The summary and detail views are identical on this resource.

Path parameters

projectintegerRequired

The Project's numeric id. Accepts a soft-deleted record.

Query parameters

Unknown parameters are refused with 400, naming the parameter.

30 parameters in 6 groups

Views

viewstring

Which field set to render.

summarydefaultdetail

Pagination

Cursor pagination only. Follow links.next.

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.

with_totalboolean

Whether meta.page.total is counted for this request.

Default: false

Filters

=: equals
[in]: any of a comma-separated list
[null]: true or false: whether it is empty
[gte][lte][lt]: at least, at most, less than
[ne]: not equal

filter[budget_id]integer=[in]

Budget the task is filed under. Combine with the project in the path to narrow a board to one budget.

A comma-separated list of at most 100 values.

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

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

filter[due_date]date (YYYY-MM-DD)=[gte][lte][null]

Day the task is due. null reaches the cards left undated in plnnrly.

Whether the field is null.

filter[is_billable]boolean

Whether time logged on this task is billable.

filter[is_finished]boolean

Whether the task is done. Kept in step with status automatically, so filter[is_finished]=true and filter[status]=finished select the same rows.

filter[status]string=[ne][in]

Kanban column the card sits in.

A comma-separated list of at most 100 values.

on-holdnewactiveinternal-testexternal-testfinished

New values may be added.

filter[team_id]integer=[in][null]

Team the task is filed under. Only plnnrly itself assigns one, so tasks created through the API always match filter[team_id][null]=true.

A comma-separated list of at most 100 values.

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

Last-write timestamp. Use for incremental sync.

filter[user_id]integer=[in][null]

Whose board to return. Accepts the literal me, and defaults to the authenticated user; naming another user requires kanban::manage_for_others.

A comma-separated list of at most 100 values.

Search

qstring

Free-text search over description. 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_column

Key	Sorts by
`order_column`	Position on the kanban board, lowest first. Server-assigned and changed when someone drags the card in plnnrly; ties are broken by id.
`due_date`	Day the task is due.
`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.

Other

trashedstring

Whether soft-deleted rows are included.

withoutdefaultwithonly

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 TaskList rows.

dataarray of TaskList

The rows, each a TaskList.

meta.pagePageOptionalTotal

per_page, next_cursor, prev_cursor, total.

linksPageLinks

self, next, prev.

Each row is a TaskList: 17 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

idinteger

Unique identifier.

budget_idinteger

Budget the task is filed under. This is the task's only link to a project (a task has no project_id of its own), and it is settable at create time only; a task cannot be re-budgeted through the API.

user_idinteger or nullServer-assigned

The employee the task belongs to. Always the authenticated user on create; not writable. Null on a task left unassigned in plnnrly.

team_idinteger or nullServer-assigned

Team the task is filed under. Nothing on the API path assigns it, so a task created through the API always carries null; plnnrly itself is the only place a team is set. Not writable, and there is no team object beside it.

due_datedate (YYYY-MM-DD) or null

Day the task is due. Required when creating a task through the API, and clearable afterwards; tasks created in plnnrly may carry null.

minutesinteger

Estimated effort, in minutes.

descriptionstring≤ 255

Short description shown on the kanban card. This is the task's label and the only field ?q= searches.

commentstring or null≤ 255

Optional longer comment on the card, capped at 255 characters.

is_finishedboolean

Whether the task is done. Cross-synced with status on every write: setting status to finished sets this true and any other status sets it false, while setting this false on a finished task moves status back to active. status wins when both are sent.

is_billableboolean

Whether time logged on this task is billable. Defaults to true when a task is created through the API, regardless of the budget's own setting.

statusstring

Kanban column the card sits in.

on-holdnewactiveinternal-testexternal-testfinished

New values may be added.

order_columnintegerServer-assigned

Position on the kanban board, lowest first. Appended to the end of the board on create and changed when someone drags the card in plnnrly. Not writable.

created_attimestamp (YYYY-MM-DDThh:mm:ssZ)

Creation timestamp.

updated_attimestamp (YYYY-MM-DDThh:mm:ssZ)

Last-write timestamp; use for incremental sync.