---
title: "Validate withdrawal address"
method: POST
path: "/payments/wallet-addresses/validate"
tags: ["Withdrawal addresses"]
---

# Validate withdrawal address

`POST /payments/wallet-addresses/validate`

## Request

- Base URL: `https://api.breet.io/v1`
- URL: `https://api.breet.io/v1/payments/wallet-addresses/validate`
- Auth: API key in header `x-app-id` and API key in header `x-app-secret` and API key in header `X-Breet-Env`
- TypeScript: <https://skmtc.dev/breet/apis/breet-public-api/docs/payments/wallet-addresses/validate/post.ts> (a function with typed inputs; its response is checked against the schema)

Check that a wallet address is correctly formed for a token and network before you submit a withdrawal. This is a format check only — it does not confirm the address exists, is reachable, or is permitted. A withdrawal to an address that passes here can still be rejected for other reasons.

## Request body

- object
  - `address` string, required: The wallet address to check.
  - `token` 'USDT' | 'USDC' | 'BTC' | 'LTC' | 'DOGE' | 'BCH', required: Token symbol.
  - `network` 'ERC20' | 'TRC20' | 'BSC' | 'SOL' | 'TON' | 'BASE': Blockchain network. Required for stablecoins. Omit it for the UTXOs BTC, LTC, DOGE, and BCH, which run on a single chain.

## Response `200`

The address is valid for the token and network

## Other responses

- `401`: Invalid or missing API credentials
- `403`: The integration is inactive or the action is not permitted
- `422`: The address is invalid, or the token and network combination is not supported
- `500`: An unexpected server error occurred

## Changes

- **2026-11-03** `41450811e16e`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/breet/apis/breet-public-api/changes/payments/wallet-addresses/validate/post.md)

---

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