connections

Call connections.request_number_purchase

Get this workspace its own texting number — 'buy us a texting number', 'get a phone number for SMS'. Buy a texting number for this workspace. It SPENDS MONEY — a number carries a recurring monthly charge — so calling it raises the approval card naming the number and its monthly charge, which is the operator's confirmation, and it buys only on their approve. Pass the exact number the operator chose. Buying a number does NOT make texting work: the number lands in compliance_pending and the operator still has to register it with the phone companies, which is a step only they can do. Say that when you offer it. Not for why texts cannot go out — that is connections.messaging_registration_status. Over the API it answers in two calls: without confirmation_id it proposes — says what would happen, returns a confirmation_id and changes, spends and sends nothing; the same arguments again with that confirmation_id, on a member's own API key, do it.

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.

post/api/v1/tools/connections.request_number_purchase

Request

  • Base URL: https://app.goosybear.ai
  • URL: https://app.goosybear.ai/api/v1/tools/connections.request_number_purchase
  • Auth: HTTP bearer

Headers

x-request-idstring

Your own id for this request, echoed back and recorded on the audit trail. 1–128 characters from A–Z a–z 0–9 . _ : -, starting with a letter or digit; anything else is replaced by a generated id.

Request body

phone_numberstring required

The number to buy, in full international format. It must be one the operator has chosen from the available list — never one you composed, and never a number the operator merely mentioned in passing.

confirmation_idstring uuid

Omit to propose: the first call says what would happen, returns a confirmation_id and changes nothing. To go ahead, send the same arguments again with that confirmation_id, on a member's own API key; a service account's key can propose but never confirm.

workspacestring

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

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.

OR

Changes

No recorded changes to this operation across all 6 revisions of this API.