/v1/boards/{id}/rowsRead a page of a board's rows
One page of a custom board's rows, narrowed by the service exactly as get_definitions_key_rows narrows a pack page: q searches every cell, filter[<column label or id>] (repeatable) keeps rows whose cell is one of the values, or contains the text after a ~ in any case (filter[Location]=~phoenix) (filter[$messages]=replied|sent keeps rows by who wrote last on their email and text threads; filter[$created]=>=2026-10-01 or $updated by when the row was made or last changed — a day, a month or an instant after >=, >, <= or <, repeated for a range, in UTC), sort + dir order by a stored column or $created / $updated, limit (default 200 when narrowed, at most 1000) and offset page. Answers {data: rows, page: {total, limit, offset}} where total is the whole narrowing's count. A filter or sort on a formula or lookup column is refused — read the board whole with get_boards_id. Read access on the board; a member on the assigned rung sees only the rows filed on them. fields names the only columns each row answers — column ids or labels, repeated or comma-separated (fields=Name,Status) — so reading many rows to export, count or summarise them carries the columns that matter instead of every cell; a field the board has no column for is refused. labels=true (a tool call's default; labels=false for ids) keys cells by column name and decodes relation/file cells. A DATE or datetime column takes the same bounds: ?filter[<its column id>]=>=2026-09-20 keeps the rows whose date is on or after the 20th (repeat for a range; a bare value is still the exact stored text) — so "deals funded in the last 30 days, and for how much" is ONE aggregates read over the Funded Date column, never the accounting ledger. dealRowId=<deal row id> keeps the rows linked to that deal on a page that links to Deals (one deal-link column), as on get_definitions_key_rows.
Access class: board:read.
Send request
Use the documented inputs to call this endpoint directly.
Parameters
Values are applied to the request and the example on the right.
one entry per column: {"": ""}, or a list to match any of several — sent as filter[]= in the query string. The key is a column's label (any case) or its id — a label two columns share is refused, send the id; the value may be a select's option label, a person's name or email, or the stored value, in any case; a value opening with ~ keeps the cells CONTAINING the text after it, any case ("~phoenix"; a literal leading ~ is sent as ~). The reserved key $messages takes replied (their email or text is the newest on the record, unanswered) or sent (ours is, no answer yet), and a date bound on when that last word was written beside it: ["sent", "<2026-10-15"] is no answer since before the 15th
Responses
the action's answer
{
"data": [
{
"assignees": {},
"cells": {},
"createdBy": "string",
"externalId": "",
"id": "",
"position": 1.5
}
],
"page": {
"limit": 1.5,
"offset": 1.5,
"total": 1.5
}
}a refusal: {"error": "<what a person needs to read>"}. 401 no credential, 402 the plan does not include this, 403 the seat does not, 404 the thing does not exist or is not yours to see.
{
"error": "string"
}