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
| Name | Type | Required | Description |
|---|---|---|---|
suiteId | string | yes |
Headers
| Name | Type | Required | Description |
|---|---|---|---|
Idempotency-Key | string | no | Any 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
| Field | Type | Required | Description |
|---|---|---|---|
hostname | string | yes | Up to 253 characters. |
Response
Success
dataobjectrequiredRefused
errorobjectrequired