#Overview
Use the rows endpoint to fetch specific rows or query rows by a column's cell value. Filtering supports limit, including limit=1 for "next item" workflows.
#Endpoint
GET /v1/lists/{tableId}/rows#Request Examples
Rows are read with query parameters rather than a JSON request body.
GET /v1/lists/tbl_123/rows?userId=usr_123&rowIds=row_123,row_456
GET /v1/lists/tbl_123/rows?userId=usr_123&index=0
GET /v1/lists/tbl_123/rows?userId=usr_123&columnId=status&operator=eq&query=pending&limit=1#Query Modes
| Query | Description |
|---|---|
rowIds=row_1,row_2 |
Fetch specific rows by ID. |
index=0 |
Fetch a row by its list index. |
columnId=status&operator=eq&query=pending&limit=1 |
Filter rows by a column's cell value. |
#Supported Operators
eq, not_eq, contains, not_contains, like, starts_with, ends_with, gt, gte, lt, lte, is_empty, and is_not_empty.
The like operator uses SQL-style wildcards: % matches any number of characters and _ matches one character. For example, query=alpha% matches alpha pending, while query=alp only matches the exact pattern alp.
#Enum Columns
For enum columns, eq matches either the option key or label. For example, an enum status column with pending, ready, and error can be queried with query=pending.
#Example: Get the Next Pending Item
curl "https://api.bigmind.ai/v1/lists/tbl_123/rows?userId=usr_123&columnId=status&operator=eq&query=pending&limit=1" \
-H "Authorization: Bearer sk_your_api_key_here"#Example Response
{
"success": true,
"data": {
"rows": [
{
"id": "row_123",
"tableId": "tbl_123",
"cells": {
"status": {
"columnId": "status",
"rowId": "row_123",
"value": "pending",
"computedValue": "pending",
"status": "completed"
}
},
"updated_at": "2026-05-14T10:00:00.000Z"
}
],
"totalMatched": 12,
"returned": 1,
"truncated": true
}
}