onboarding

Onboarding Reach Mobile

Changed on

HIS MOBILE, PROVED ON THE SETUP CARD, REACHES STORMY (owner, 2026-10-13, asked to text a code right after typing the one his phone got: "why do we ask him to send it again??").

The card texts a code to the mobile he typed and the code back signs him in by it (HireMobileAsk), so Supabase holds it confirmed on his login. Where the routing already places that mobile on this workspace (one owner, one workspace) nothing is written; where it cannot (he owns several, or this one has no contact row yet) it is linked here, as his code texted from it would link it (system_number_link.link_proved). Only his own confirmed mobile, only to a workspace he owns, never the founder's number (his texts are the system seat's).

post/v1/teams/{team_id}/onboarding/reach/mobile

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}/onboarding/reach/mobile
  • Auth: none declared

Path parameters

team_idstring uuid required

Headers

authorizationstring nullable
x-darwin-tokenstring nullable

Response

Successful Response

object required

Changes