Account Center › API Reference › Merchant Account

Your withdrawal address book (read-only; no POST)

GET /v1/merchant/payout-addresses scope: merchant:read

Merchant account

⚠ The Open API has no write endpoint for this resource, deliberately rather than because it is unfinished. Withdrawal addresses can be added only through the merchant portal, which enforces step-up authentication and a 24-hour cooling period. A machine API can enforce the cooling period but cannot ensure a human second factor: an API Key is a persistent credential, with no second factor or proof that someone is physically present at a screen. Adding a payout destination is the most direct way to withdraw funds after account takeover.

This page therefore answers only: which addresses exist and which can be used now.

usable is the boolean decision; usable_at is when the cooling period ends. Withdrawals to an address still cooling are rejected. A timestamp alone would require you to compare clocks, and users without this flag might assume a newly added address is ready, then be rejected without knowing why.
Revoked addresses are omitted. Revocation retains the row but removes it from this list.
asset / network / label may be empty strings, because these fields are optional when adding an address through the portal. Do not match an empty network against your own network enum.

Not paginated; next_cursor is always null.

Parameters

This endpoint takes no parameters: no path parameters, query parameters or request body. For the authentication header (x-auth-token) and on-behalf-of header (x-on-behalf-of), see Authentication and Signing.

Response

200OK

{
  "data": [
    {
      "id": "3f9c1a5e-88b1-4b0e-9a2d-7c1f0e5b4a33",
      "asset": "USDT",
      "network": "BSC",
      "address": "0x5aAeb6053F3E94C9b9A09f33669435E7Ef1BeAed",
      "label": "结算主地址",
      "usable": true,
      "usable_at": "2026-08-12T03:20:00.000Z",
      "created_at": "2026-08-11T03:20:00.000Z"
    }
  ],
  "next_cursor": null,
  "has_more": false
}

403insufficient_scope: missing merchant:read.

Request

curl -X GET 'https://api.zinfra.vip/v1/merchant/payout-addresses' \
  -H 'x-auth-token: Bearer $TOKEN'

const res = await fetch("https://api.zinfra.vip/v1/merchant/payout-addresses", {
  method: "GET",
  headers: {
    "x-auth-token": "Bearer $TOKEN",
  },
});
// Keep monetary amounts as strings, never numbers.
const data = await res.json();

import requests

res = requests.get(
    "https://api.zinfra.vip/v1/merchant/payout-addresses",
    headers={
        "x-auth-token": "Bearer $TOKEN",
    },
)
# Use Decimal(str(...)) for amounts, not float.
data = res.json()

req, _ := http.NewRequest("GET", "https://api.zinfra.vip/v1/merchant/payout-addresses",
    nil)
req.Header.Set("x-auth-token", "Bearer $TOKEN")
res, err := http.DefaultClient.Do(req)
// Decode amount fields as string, not float64.

HttpRequest req = HttpRequest.newBuilder()
    .uri(URI.create("https://api.zinfra.vip/v1/merchant/payout-addresses"))
    .header("x-auth-token", "Bearer $TOKEN")
    .method("GET", HttpRequest.BodyPublishers.noBody())
    .build();
// Use String / BigDecimal for amounts, not double.

$ch = curl_init('https://api.zinfra.vip/v1/merchant/payout-addresses');
curl_setopt_array($ch, [
  CURLOPT_CUSTOMREQUEST => 'GET',
  CURLOPT_RETURNTRANSFER => true,
  CURLOPT_HTTPHEADER => [
    'x-auth-token: Bearer $TOKEN',
  ],
]);
$res = curl_exec($ch);
// Use bcmath / strings for amounts, not floatval.

200

{
  "data": [
    {
      "id": "3f9c1a5e-88b1-4b0e-9a2d-7c1f0e5b4a33",
      "asset": "USDT",
      "network": "BSC",
      "address": "0x5aAeb6053F3E94C9b9A09f33669435E7Ef1BeAed",
      "label": "结算主地址",
      "usable": true,
      "usable_at": "2026-08-12T03:20:00.000Z",
      "created_at": "2026-08-11T03:20:00.000Z"
    }
  ],
  "next_cursor": null,
  "has_more": false
}