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

# Call connections.messaging_registration_status

`POST /api/v1/tools/connections.messaging_registration_status`

## Request

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

Check whether this workspace can send texts and what's standing in the way — 'why can't we send texts', 'what's blocking our SMS'. Read whether this workspace can send texts and what is standing in the way. Call it before answering ANY question about texting, SMS, or a phone number — a workspace can own a number and still be unable to send, because the phone companies register senders separately, and that is the single most common surprise here. Read `can_send_texts` first and `why_not` second. Not for buying a texting number — that is `connections.request_number_purchase`.

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
  - `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
    - `state` 'none' | 'number_pending' | 'compliance_pending' | 'submitted' | 'approved' | 'rejected', required: `none` — this workspace has never started; there is no number. `number_pending` — started, no number yet. `compliance_pending` — the number IS bought and real, but the phone companies have not approved it, so texts do NOT go out. `submitted` — filed and under review. `approved` — texting is live. `rejected` — turned down, and `rejection_reason` says why. NEVER report `compliance_pending` as connected or working.
    - `can_send_texts` boolean, required: True for `approved` only. When false, `why_not` is the sentence to give the operator — do not paraphrase it into something more hopeful.
    - `why_not` string, nullable, required
    - `headline` string, required
    - `next_action` string, nullable, required: What has to happen next, in the operator's words. Null means nobody's move — a wait on the phone companies. Never invent one.
    - `has_number` boolean, required
    - `number_purchased_at` string, nullable, required
    - `rejection_reason` string, nullable, required: The phone companies' own words, on `rejected` only. Quote it — it is what tells the operator what to fix.
    - `registration_steps` object[], required: The five steps the operator performs themselves in their Grow account. We cannot file the registration for them — there is no API for it — so never offer to.
      - `position` integer, required
      - `title` string, required
      - `why` 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/0e033701d3f7?raw)