gtable
gtable.appOpen the Studio
DomainsAttach a hostname to a suite
Domains

Attach a hostname to a suite

Routes a hostname to this suite: its people sign in there, and each of its apps answers underneath at its own slug, /crm, /hr.

POST/v1/suites/{suiteId}/domains

A suite is one front door, so one address serves every app in it. The suite’s own platform subdomain is active at once. Any other hostname is a domain of your own, a paid option, and subdomains only (app.example.com, not example.com), and starts pending: the answer carries a TXT record that proves you own it and a CNAME that sends traffic here. Publish both, then call domains.verify: once the TXT shows, the hostname is provisioning while a certificate is issued, and active when it serves. A hostname another organisation answers on is refused.

Requires the schema:write scope. Operation domains.attach. MCP tool domains_attach. CLI, once published: gtable domains attach.

Path parameters

NameTypeRequiredDescription
suiteIdstringyes

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
hostnamestringyesUp to 253 characters.

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.