Skip to main content
POST
Query a listing's row IDs

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

table_id
string<uuid>
required

Body

application/json

Request body for the row-ID manifest.

The same listing vocabulary as the rows query, minus the projection: this asks which rows a listing selects and in what order, not what is in them. Answering it reads no cell payload, so a client can hold a whole table's ordering cheaply and then hydrate only the window it is showing.

cursor
string | null

Opaque cursor from a previous page's next_cursor.

Maximum string length: 1024
limit
integer
default:10000

Maximum record IDs per page. Far higher than the rows query's limit because a page of IDs carries no cells.

Required range: 1 <= x <= 10000
offset
integer | null

Start the listing this many rows in. Mutually exclusive with cursor.

Required range: x >= 0
row_status
enum<string> | null

Restrict to rows whose cells are errored or fully_computed.

Available options:
errored,
fully_computed
sorts
TableRowSortSchema · object[]

Order by these columns, in priority order, instead of display order.

Maximum array length: 3
where
TableRowsWhereSchema · object | null

The predicate tree every returned row must satisfy.

Response

Successful Response

One keyset page of a listing's record IDs, in order.

has_more
boolean
required
limit
integer
required
next_cursor
string | null
required

Cursor for the next page; None when this is the last page.

record_ids
string<uuid>[]
required