Get a wallet

Returns a wallet you created, looked up by the id from its creation response.

Endpoint

GET https://merchant.minisend.xyz/api/v1/wallets/{walletId}

Authorization: Bearer wsk_live_your_key_here

The path segment is the wallet’s id — a UUID — not its wallet_ref. Wallets belonging to another account return 404, and so does a value that isn’t a well-formed UUID, so a 404 handler catches the “I passed a ref by mistake” case too. There is no lookup-by-wallet_ref endpoint. Since the ref is your own identifier, re-POST it to create wallet instead: that call is create-or-get and returns the existing wallet.

Example

curl https://merchant.minisend.xyz/api/v1/wallets/3f6b2e1a-... \
  -H "Authorization: Bearer wsk_live_your_key_here"

Response (200)

{
  "wallet": {
    "id": "3f6b2e1a-...",
    "tenant_id": "a7c9e2d0-...",
    "master_wallet_id": "d4f81b3c-...",
    "wallet_ref": "user-9214",
    "address": "0xabc1230000000000000000000000000000dead",
    "chain": "BASE",
    "status": "active",
    "mode": "live",
    "metadata": null,
    "created_at": "2026-07-29T09:00:00.000Z"
  }
}

Same shape as create wallet’s response.

Errors

Status	Meaning
`401`	Missing or invalid API key
`404`	Unknown wallet, one belonging to another account, or a path segment that isn’t a UUID

Overview

Endpoints

Off-ramp endpoints

Onramp endpoints

Wallet API endpoints

Get a wallet

Endpoint

Example

Response (200)

Errors

​Endpoint

​Example

​Response (200)

​Errors

Endpoint

Example

Response (200)

Errors