---
title: "Onboarding Reach Mobile"
method: POST
path: "/v1/teams/{team_id}/onboarding/reach/mobile"
tags: ["onboarding"]
---

# Onboarding Reach Mobile

`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

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).

## 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

## Changes

> 68 revisions in range; 1 not diffed.

- **2026-10-13** `f926858b5ed4`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/stormy/apis/stormy-control-plane/changes/v1/teams/:team_id/onboarding/reach/mobile/post.md)

---

[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/a40e83844eaa?raw)