List project tickets

Project ID

Page number (1-indexed)

How many tickets per page, 1 to 100; 50 when omitted. Pass limit=1 when you only need pagination.total and byStatus.

Return only the tickets in these columns — one, or several separated by commas (status=todo,in_progress). Omit it for every column. byStatus ignores this filter, so its counts still cover every column, narrowed by every other filter you passed.

The order of the list. board (the default) is the board flattened: the columns in board order, each in the order the team keeps — and the only order to read neighbours for a move from. priority puts the highest impact first; among the same impact, the least effort first, and among the same effort the fewest minutes of the edition's estimate; then the earliest due date, then board order. A missing value sorts last at each step. due puts the earliest due date first, undated last. activity puts the most recently touched first (lastActivityAt). Any order but board mixes the columns; each ticket carries its status.

How much of done and dismissed to return. all (the default) returns them whole; recent returns only the tickets that reached those columns within the last 30 days. The other columns are always whole, whichever you pass, and a read narrowed to one edition is whole whatever you pass.

Who opened the ticket, never which dimension it is about (that is dimension): user — a person in the app; api — an API key, which is what everything you write here carries; briefing — a Strategic Briefing; ai_sources — reserved for a future AI Sources writer, which opens none today, so that value matches none.

Return only the tickets a Strategic Briefing opened for one part of its analysis, or none for the tickets no part claims — everything a person or an API key opened, and a briefing's ticket whose edition named none. agent-readiness is the key for Agent Adoption — how well a site is set up for AI agents to discover, access and read it. The key predates the name and does not change.

Return only the tickets one Strategic Briefing edition opened. Take the id from GET /v1/projects/{projectId}/strategic-briefing/history, or from meta.runId on a briefing read. Nothing a person or an API key opens carries an edition, so this narrows the list to that edition's tickets whether or not you also pass origin. An edition's tickets are returned whole, the finished and dismissed ones included however long ago they were closed — closed has no effect on this read — so the list matches the count the briefing states for that edition.

Return only the tickets one person owns — their user ID, from GET /v1/projects/{projectId}/tickets/assignees. Pass none for the tickets nobody owns. A ticket whose owner has left the organization reads as unassigned everywhere, but is still found here by their ID.

Return only the tickets carrying one label — its ID, from GET /v1/projects/{projectId}/tickets/labels. A project's list is empty until the project defines a label, in the app or through POST /v1/projects/{projectId}/tickets/labels.

Return the one ticket carrying this number on the board — what a person means by #14. It is a name and not an address: this narrows the list, and every endpoint that acts on a ticket still takes its id.

Return only the tickets whose title or description contains this text, compared without regard to case. It is matched literally — punctuation is text, not a pattern — and threads are not searched. A match in a description is weaker evidence than one in the title: a briefing's description quotes its grounding, so read the ticket before calling two tickets the same work.

Return only the tickets whose impact is at least this, 1 to 4 (1 Minor · 2 Moderate · 3 Significant · 4 Critical; 4 matters most). Tickets nobody sized are left out. A Strategic Briefing sets impact and effort on the tickets it opens, so a value there is the edition's estimate until a person changes it.

Return only the tickets sized as one of these — one, or several separated by commas (effort=low,medium). Tickets nobody sized are left out. This is the ticket's size word, not its minutes: a briefing's briefing.estimatedMinutes is the edition's own time estimate, neither is derived from the other, and a low ticket can be an afternoon — when a person asks for something quick, use maxMinutes.

Return only the tickets a Strategic Briefing opened whose edition estimated at most this many minutes of work. A ticket without an edition's estimate — everything a person or an API key opened, and a briefing's ticket the edition did not size — is left out; use effort for those.

Return only the tickets due on or after this calendar day, YYYY-MM-DD. Tickets with no due date are left out. A due date has no time zone, so pass the customer's own day.

Return only the tickets due strictly before this calendar day, YYYY-MM-DD. dueBefore=<today> with the open columns (status=triage,todo,in_progress) is everything overdue; with dueFrom it is a range. Tickets with no due date are left out. A due date has no time zone, so pass the customer's own day.

Return only the tickets something happened to at or after this moment — an edit, a move, or a new thread entry (lastActivityAt). ISO 8601 with its offset; a time without one is read as UTC, and YYYY-MM-DD is the start of that day in UTC. A deleted ticket is gone and does not appear.

What each ticket in the list carries. By default a list is an INDEX: every field except the ticket's own Markdown description, which is then not on the row at all. Pass include=description for the bodies — one ticket's description runs to thousands of characters, so a page fetched with them is large enough to be worth asking for on purpose. GET …/tickets/{ticketId} always returns the description whatever you pass here.