phone numbers

Shared Onboarding Status

Is the shared Stormy number armed, and can this workspace be rung on it?

AND IT FINISHES OUR OWN FILING WHILE IT IS HERE (repair=True). Asking whether a workspace can be rung is the moment to make the answer true where the only thing missing is a row we owe it: the mirror is bookkeeping, not a carrier effect (no provider resource, no A2P filing, capabilities: []), and it is written once per workspace and never again. Without this, every workspace created before the number was armed answers false forever — signup is the only other caller, and a cross-team backfill has no plane to run on.

A repair that fails is reported (repair_error) and changes nothing else: the answer stays an honest reachable: false rather than a 500.

get/v1/teams/{team_id}/phone/numbers/shared

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/shared
  • Auth: none declared

Path parameters

team_idstring uuid required

Headers

authorizationstring nullable
x-darwin-tokenstring nullable

Response

Successful Response

object required

Changes

No operation changes recorded.