---
title: "Call domain.set_use"
method: POST
path: "/api/v1/tools/domain.set_use"
tags: ["domain"]
---

# Call domain.set_use

`POST /api/v1/tools/domain.set_use`

## Request

- Base URL: `https://app.goosybear.ai`
- URL: `https://app.goosybear.ai/api/v1/tools/domain.set_use`
- Auth: HTTP bearer

Set one of the member's domains up for sending email, branded links, or funnels and sites — 'use this domain for my emails', 'set up my links domain', 'I want funnels on my own address'. Set a domain up for one of Goosy Grow's uses: mail (sending email), crm_links (branded links in emails and texts), or funnel (funnels and sites). Where we manage the domain's DNS we add the records for the customer; where we do not, we work out exactly which records they need. Either way ONE step is always theirs: opening Goosy Grow and adding the domain on the screen this returns. ALWAYS relay the copy_card lines and the deep_link — that is the point of the call — and never say the setup is finished, because it is not until they have clicked and domain.status confirms it. outcome zone_not_held and records_from_grow_screen are normal answers, not errors. Not for pointing a domain at a site — that is `domain.connect`.

Every result names the workspace it ran in. Say which workspace the answer is about. When the account has more than one workspace and none is selected, this tool refuses with `workspace_ambiguous` and lists the choices — offer them, never pick one.

## Headers

- `x-request-id` string

## Request body

- object
  - `domain_id` string, uuid, required: The domain, as a UUID. Take it from the conversation's context or from the workspace's domain list — never invent one.
  - `use` 'mail' | 'crm_links' | 'funnel', required: What the domain should be used for in Goosy Grow: `mail` (sending email), `crm_links` (the branded links in emails and texts), or `funnel` (funnels and sites).
  - `workspace` string: Which workspace to run in — its slug. Omit to use your default. With more than one reachable workspace and no default, the call is refused and the choices are listed.

## Response `200`

The call was admitted and dispatched. `ok` says whether the tool succeeded — a refusal the tool itself produced is still a 200, exactly as it is a successful JSON-RPC result over MCP.

- union
  - object: The tool ran and answered.
    - `ok` true, required
    - `domain_id` string, uuid, required
    - `hostname` string, required
    - `use` 'mail' | 'crm_links' | 'funnel', required
    - `state` string, required
    - `outcome` string, required
    - `deep_link` string, nullable, required
    - `screen` string, required
    - `screen_path_verified` boolean, required
    - `records` object[], required
      - `type` string, required
      - `name` string, required
      - `value` string, required
      - `source` string, required
    - `copy_card` string[], required
    - `workspace` string, required: The slug of the workspace this call ran in.
    - `working_in` object, required: Which workspace this call ran in, and how that was decided. Present on every workspace-scoped result.
      - `label` string, required: The chip words — e.g. "working in: Acme Main".
      - `note` string, required: Why this workspace — e.g. "your default", "this call only".
      - `workspace` string, required: The resolved workspace's slug.
      - `source` 'call-override' | 'key-pin' | 'stored-default' | 'sole-reachable', required: Which rung of the R7 precedence resolved the workspace.
  - ToolRefusal: A call that was admitted and dispatched, and did not succeed.
    - `ok` false, required
    - `code` string, required: The typed reason — e.g. `workspace_ambiguous`, `invalid_arguments`, or the tool's own failure code.
    - `message` string, required: A sentence a person can act on.
    - `workspaces` string[]: On a workspace refusal: the slugs this key may pass as `workspace`.
    - `issues` object[]: On `invalid_arguments`: which fields failed, and why.
      - `path` string, required
      - `message` string, required
    - `path` string: On an authoring refusal: where in your call's input it points, e.g. `steps.<key>.params.<field>`.
    - `fix` string: On an authoring refusal: the change to your call that would pass.
    - `instruction` string: On an authoring refusal: what to do next with it.

## Other responses

- `400`: The request could not be used: the body is present but not a JSON object (`tenant_api.malformed_body`); it is a top-level array carrying more messages than this endpoint accepts (`tenant_mcp.batch_too_large`); or the `Idempotency-Key` header is malformed (`tenant_api.idempotency_key_invalid`), disagrees with the body's `idempotency_key` (`tenant_api.idempotency_key_conflict`), or was sent to an action that cannot replay a retry (`tenant_api.idempotency_unsupported`). Nothing ran.
- `401`: No bearer credential, or one that did not resolve. Deliberately ONE undifferentiated answer for absent / unknown / revoked / expired, so the endpoint is never an oracle over the key space.
- `403`: The credential is good but the surface is not open to it — the platform or account API switch is off, or the holder lacks the `api.access` capability. The `code` says which.
- `404`: No such tool. The body names no tool and is identical for every unrecognised name.
- `429`: Over this key's per-minute cap. Carries `Retry-After` and `error.retry_after_seconds`.

---

[API](https://skmtc.dev/goosybear/apis/goosy-bear-api.md) · [All operations](https://skmtc.dev/goosybear/apis/goosy-bear-api/llms.txt) · [OpenAPI document](https://skmtc.dev/goosybear/apis/goosy-bear-api/revisions/6d82fb124064?raw)