Grid82
grid82.comJoin the waitlist
RecordsRead a window of records by position

Read a window of records by position

Rows offset to offset + limit of the set a list would return, in the same order, with the size of the whole set.

GET/v1/tables/{tableId}/records/window

Meant for a grid that scrolls; to walk a table use records.list and its cursor, which cannot skip or repeat a row when somebody writes in between.

Requires the records:read scope. Operation records.window. Not an MCP tool. A positional read for a grid that scrolls: it addresses rows by offset, which can skip or repeat a row when somebody writes between two calls. A model walks a table with records.list and its cursor, which cannot, and asks records.count for the size. CLI: grid82 records window (npx grid82).

Path parameters

NameTypeRequiredDescription
tableIdstringyes

Query parameters

NameTypeRequiredDescription
viewIdstringnoUp to 64 characters.
searchstringnoUp to 200 characters.
filterstringnoUp to 4000 characters.
sortsstringnoUp to 1000 characters.
wherestringnoUp to 4000 characters.
offsetintegernoDefault 0.
limitintegernoDefault 100.

Response

application/json

Success

dataobjectrequired

Use these docs with your AI tools

An AI agent can read this documentation directly. You do not need an account or an API key. Everything here is public and read-only.

Query these docs via MCP

Recommended

Add this server to Claude, Claude Code, Cursor, Mistral, or any tool that supports MCP. Your agent can then search Grid82 documentation and read it in full, instead of answering from memory.

https://grid82.com/docs/mcp
  • searchFind the passages that answer a question.
  • fetchRead one page in full, as Markdown.
  • list_pagesSee every page in this documentation.

Query these docs over HTTP

The same tools also work as plain web requests. Use this for scripts, or for any tool that does not support MCP. There is one endpoint per tool. Arguments go in the query string, and the answer comes back as JSON.

https://grid82.com/docs/api/docs/search?query=custom+domain

Read the OpenAPI description. It is built from the same definitions as the tools, so it always matches what the endpoints do.

Read these docs as Markdown

Add .md to any page URL to get its Markdown source. You can also send the headerAccept: text/markdown to the page URL itself.

To read the whole documentation in one file, open llms-full.txt. For a short index of every page, open llms.txt.