gtable
gtable.appOpen the Studio
REST APIEvents and webhooks

Events and webhooks

Pull what changed in an app since the last event you saw. Webhooks are not available yet; the events feed is how you follow changes today.

Pull what changed

The events feed lists what changed in an app, oldest first, from the last event you saw:

HTTP
GET https://your-suite.gtable.app/your-app/v1/events?since=chg_01J…&limit=200

Pass meta.nextCursor back as cursor while meta.hasMore is true, and keep the last id you processed for next time. since and cursor both mean “the last change I saw”.

Events go through your permissions like a read:

  • a row you cannot see produces no event for you;
  • a field you cannot read is absent from the events you do get;
  • a deleted row is reported as the bare fact that it went, never its former contents;
  • someone who is not a member of the app is refused, rather than handed an empty feed.

Builders follow changes from the Studio’s change list (GET /v1/apps/{appId}/changesets); there is no builder events feed.

Webhooks

Not available yet. gtable does not send webhooks today. When it does, deliveries will follow Standard Webhooks: a signed id, timestamp and body, verifiable with any Standard Webhooks library, retried with backoff. The events feed above is how a webhook consumer will catch up after being down, so code written against it keeps its value.

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.