---
title: "POST /v2/me/wallet-link/authorize"
method: POST
path: "/v2/me/wallet-link/authorize"
tags: ["Identity"]
---

# POST /v2/me/wallet-link/authorize

`POST /v2/me/wallet-link/authorize`

## Request

- Base URL: `https://api.arbital.xyz` (the document declares no server; this is the origin it was published from)
- URL: `https://api.arbital.xyz/v2/me/wallet-link/authorize`
- Auth: HTTP bearer

Proves that the current social login is the exact surviving parent authorized for a pending Privy account transfer.

## Request body

- object
  - `recovery_token` string, required

## Response `200`

The exact surviving parent is authorized to receive the wallet

- object
  - `expires_at` string, date-time, required
  - `recovery_token` string, required
  - `state` 'authorized', required
  - `wallet_address` string, required

## Other responses

- `400`: Stable machine-readable problem. HTTP 429 and 503 responses include retry and cache-validity fields plus Retry-After and X-Request-ID headers.
- `401`: Stable machine-readable problem. HTTP 429 and 503 responses include retry and cache-validity fields plus Retry-After and X-Request-ID headers.
- `403`: Stable machine-readable problem. HTTP 429 and 503 responses include retry and cache-validity fields plus Retry-After and X-Request-ID headers.
- `409`: Stable machine-readable problem. HTTP 429 and 503 responses include retry and cache-validity fields plus Retry-After and X-Request-ID headers.
- `410`: Stable machine-readable problem. HTTP 429 and 503 responses include retry and cache-validity fields plus Retry-After and X-Request-ID headers.
- `503`: Stable machine-readable problem. HTTP 429 and 503 responses include retry and cache-validity fields plus Retry-After and X-Request-ID headers.

---

[API](https://skmtc.dev/arbital/apis/arbital-api.md) - [All operations](https://skmtc.dev/arbital/apis/arbital-api/llms.txt) - [OpenAPI document](https://skmtc.dev/arbital/apis/arbital-api/revisions/bb0185edf43a?raw)