---
title: "Bind Phone Send"
method: POST
path: "/api/user/profile/bind-phone-send"
---

# Bind Phone Send

`POST /api/user/profile/bind-phone-send`

Mint + send an OTP to the target phone for the caller to verify.

Pre-flight rejects if the phone is already bound to a DIFFERENT
user (409). Re-binding the SAME phone the caller already owns is
allowed — useful as a "re-verify" affordance.

Shares the phone_otp_codes table + 60s per-phone cooldown with
/api/auth/sms/send; the OTP minted here can also be consumed by
that endpoint and vice versa. The /confirm endpoint below is the
only thing that enforces who-owns-what at verify time, so cross-
flow OTP use is benign.

## Headers

- `authorization` string, nullable

## Request body

- BindPhoneSendIn
  - `phone` string, required

## Response `200`

Successful Response

- object

## Other responses

- `422` — Validation Error

---

[API](https://skmtc.dev/omicos/apis/omicos-server.md) · [All operations](https://skmtc.dev/omicos/apis/omicos-server/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/omicos/omicos-server/revisions/a00b94573ffe/schema)
