onboarding

Onboarding Reach

Changed on

WHERE HE TEXTS STORMY (owner, 2026-10-11: "stormy has a phone number and it has slack not exclusive").

Stormy's own number (system_phone.py) — a text to it from an owner's verified mobile reaches that owner's own workspace (operations/system_conversation.py). reaches asks the very lookup the routing asks, so the first screen can never promise a text the number would drop.

THE SCREEN MUST ASK HIM TO TEXT IT (owner, same day: "during onboarding we MUST ask the user to message stormy at the phone number"), and nine in ten owners have no verified mobile, so an owner also gets code: the text the screen opens carries it and links the mobile it comes from (operations/system_number_link.py). texted_at / answered are what the screen watches to say his text arrived and Stormy answered it; linked_suffix is the mobile a code linked.

get/v1/teams/{team_id}/onboarding/reach

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

Path parameters

team_idstring uuid required

Headers

authorizationstring nullable
x-darwin-tokenstring nullable

Response

Successful Response

object required

Changes