---
title: "Phone Number Readiness"
method: GET
path: "/v1/teams/{team_id}/phone/numbers/readiness"
tags: ["phone numbers"]
---

# Phone Number Readiness

`GET /v1/teams/{team_id}/phone/numbers/readiness`

## Request

- Base URL: `https://api.stormy.ai` (the document declares no server; this is the origin it was published from)
- URL: `https://api.stormy.ai/v1/teams/{team_id}/phone/numbers/readiness`
- Auth: none declared

Whether this team can actually use a phone line — including texting.

IT NOW ANSWERS THE REGISTRATION QUESTION TOO, and that is the whole point.
Measured in the gym on 2026-08-18: asked to text a customer, the desk called
this verb twice, got a green answer, sent the message, and told the owner
"All set — I just sent the reminder." The shop was not registered, so US
carriers would have dropped it silently. The verb a desk reaches for when it
wonders "can we text" said nothing about the one thing that stops texts.

A readiness check that is green while the thing is not ready is worse than
no check, because it ends the enquiry.

## Path parameters

- `team_id` string, uuid, required

## Headers

- `authorization` string, nullable
- `x-darwin-token` string, nullable

## Response `200`

Successful Response

- object

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/stormy/apis/stormy-control-plane.md) · [All operations](https://skmtc.dev/stormy/apis/stormy-control-plane/llms.txt) · [OpenAPI document](https://skmtc.dev/stormy/apis/stormy-control-plane/revisions/4d811ab18158?raw)
