Read grid data
Reads what is inside a grid: its columns, its rows, a single cell, the run behind a computed cell, or the rows matching a search.
Example: Read a grid’s columns, or fetch a page of its rows limited to certain columns.
Usage: Set view to what you want to read and always pass the grid id. columns lists the grid’s columns; rows returns the data a page at a time (up to 200, 50 by default) and can be limited to certain columns or specific rows; cell and cell_run open one cell (both need the row id and column id, and cell_run also needs the run id); row_search finds rows matching your text (needs the search text).
Response: columns come back with their names and types; rows come as a page of cell values tagged with the grid version; a cell returns its value, status, and the run that produced it; a cell run returns its inputs, status, and version; a search returns the row-and-column matches.
Headers
Body
view: Which grid data slice to return: columns, rows, cell (needs row_id/column_id), cell_run (that cell's producing run - needs row_id/column_id/workflow_run_id), or row_search. Prefer cell/cell_run over rows+page_size=1 for a single-row/cell question - but only for expandable (blob-backed) columns, e.g. workflow/output columns with markdown/json/array/file content; plain scalar columns (text/number/boolean/single_select) already return their full value via rows and have no cell view to expand. One of: columns, rows, cell, cell_run, row_search.
columns, rows, cell, cell_run, row_search Response
Successful Response