gtable
gtable.appOpen the Studio
REST APIVersioning

Versioning

The API is versioned in its path and announces its contract version on every response. How deprecation works, and how page code is versioned.

The API

The version is in the path: /v1. Every response names the contract version that answered in the x-gtable-api-version header, and the OpenAPI document carries the same number in info.version.

  • Additive changes ship without a new path: a new operation, a new optional parameter, a new key in a response. Write clients that ignore keys they do not know.
  • Operation names never change silently. They are also the MCP tool names and the CLI commands, so renaming one would break agents and scripts without warning. An operation being retired is marked deprecated in the reference and answers with a Deprecation header and a Link to what replaces it. Once it has a date after which it may stop answering, a Sunset header says when. No operation is deprecated today.
  • Renaming or removing a key in a body or a query goes through the same deprecation.
  • A breaking change to many operations at once would be a new path, /v2.

Pages

A page’s code is stored as immutable versions. Every save builds a new version and keeps the old ones; publishing points the page at one of them. So:

  • rolling back is publishing an older version, with no rebuild;
  • two people using a page during a publish each keep the version they loaded;
  • pages.versions lists every version with who saved it, when, and whether it built.
HTTP
GET  /v1/apps/{appId}/pages/{pageId}/versions
POST /v1/apps/{appId}/pages/{pageId}/publish      { "version": 4 }

To keep editing from an older version, read its code with GET …/code?version=4 and save it as a new version.

Records

Every write appends to the app’s history: who, when, how it arrived, and the record before and after. See Undo and history.

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 gtable documentation and read it in full, instead of answering from memory.

https://gtable.app/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://gtable.app/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.