gtable
gtable.appOpen the Studio
App APIUpload a file for an attachment field
Files

Upload a file for an attachment field

Two steps, on purpose.

POST/v1/tables/{tableId}/files

This one takes the BYTES and answers with a descriptor: { id, name, size, mime, key, uploadedAt }. Writing that descriptor into an attachment field is an ordinary record write, so a file lands on a record through the same permission check, the same op log and the same undo as any other value. Send the file as multipart/form-data under file; recordId says which record it will belong to, so an upload that is never used can be swept. A descriptor you did not get from here is refused: its key names an R2 object, and inventing one would be naming somebody else’s bytes.

Requires the records:write scope. Operation files.upload. Not an MCP tool: a file is bytes and a tool call is JSON; upload with REST or the CLI. CLI, once published: gtable files upload.

Path parameters

NameTypeRequiredDescription
tableIdstringyes

Headers

NameTypeRequiredDescription
Idempotency-KeystringnoAny unique string. Sending the same key with the same request again returns the first response (marked Idempotency-Replayed: true) instead of running it twice. Reusing it for a different request is refused with 409. Kept for 24 hours. Up to 255 characters.

Request body

Sent as multipart/form-data.

FieldTypeRequiredDescription
filestringyesThe bytes.
recordIdstringyesThe record the file will be attached to, so an upload never attached can be swept.

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 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.