gtable
gtable.appOpen the Studio
FieldsChange a field's name, type, width or options
Fields

Change a field's name, type, width or options

Its id never changes: the id IS the column.

PATCH/v1/apps/{appId}/tables/{tableId}/fields/{fieldId}

config is merged into the field’s existing settings, and is checked against the type it will have after this call. Its TYPE may change, and the values are converted in the same transaction, anything that reads as the new type is kept, anything that does not is emptied rather than guessed at. A type change can break an interface page, a view’s filter or a permission condition written against the old type, so say what it will do before you propose one. Converting to or from a relation is refused: add the new field and delete the old one. Select options are replaced wholesale; keep an option’s id to keep the rows that hold it, and a removed option leaves its old values in place.

Requires the schema:write scope. Operation fields.update. MCP tool fields_update. CLI, once published: gtable fields update.

Path parameters

NameTypeRequiredDescription
appIdstringyes
tableIdstringyes
fieldIdstringyes

Query parameters

NameTypeRequiredDescription
acknowledgebooleanno

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

FieldTypeRequiredDescription
namestringnoUp to 120 characters.
type“text” or “longtext” or “email” or “url” or “phone” or “json” or “number” or “currency” or “percent” or “rating” or “duration” or “select” or “multiselect” or “checkbox” or “user” or “attachment” or “date” or “recordId” or “autonumber” or “createdTime” or “createdBy” or “modifiedTime” or “modifiedBy” or “link” or “lookup” or “rollup” or “formula” or “button”no
widthintegernoAt least 60. At most 900.
configobjectno

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.