---
title: "phoneVerificationClaim"
method: POST
path: "/onboarding/phoneVerificationClaim"
tags: ["onboarding"]
---

# phoneVerificationClaim

`POST /onboarding/phoneVerificationClaim`

## Request

- Base URL: `https://docs.wowinvoice.io`
- URL: `https://docs.wowinvoice.io/onboarding/phoneVerificationClaim`
- Auth: API key in header `authorization`

Claims the new verified login phone after Twilio approves its OTP. The existing login phone remains active until this succeeds.

## Request body

- object
  - `code` string
  - `country_code` string
  - `country_iso` string
  - `phone` string
  - `device_id` string

## Response `200`

Claims the new verified login number. data.user includes account_type, has_verified_recovery_email, and the updated verified_phones array.

- SuccessEnvelope
  - `status` 'success', required
  - `statusCode` integer, required
  - `message` string, required
  - `data` object, required
  - `error` unknown, required

## Other responses

- `400`: Standard API error envelope.
- `401`: Standard API error envelope.
- `403`: Standard API error envelope.
- `409`: Standard API error envelope.
- `422`: Standard API error envelope.

## Changes

- **2026-10-14** `303b7b41cadd`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/wowinvoice/apis/wow-invoice-internal-api/changes/onboarding/phoneVerificationClaim/post.md)

---

[API](https://skmtc.dev/wowinvoice/apis/wow-invoice-internal-api.md) - [All operations](https://skmtc.dev/wowinvoice/apis/wow-invoice-internal-api/llms.txt) - [OpenAPI document](https://skmtc.dev/wowinvoice/apis/wow-invoice-internal-api/revisions/303b7b41cadd?raw)