Attach a hostname to a suite
Route a hostname to this suite so people can sign in there and each app responds under its slug, such as /crm or /hr; one address serves every app.
POST/v1/suites/{suiteId}/domains
The platform subdomain is active immediately. Custom hostnames are a paid option and must be subdomains, such as app.example.com, not example.com; they start as pending, and the response includes a TXT record to prove ownership and a CNAME to route traffic here. Publish both records, then call domains.verify: after the TXT record appears, the hostname becomes provisioning while a certificate is issued, then active when it serves. Refuse hostnames already answered by another organisation.
Requires the schema:write scope. Operation domains.attach. MCP tool domains_attach. CLI: grid82 domains attach (npx grid82).
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