> ## Documentation Index
> Fetch the complete documentation index at: https://docs.minisend.xyz/llms.txt
> Use this file to discover all available pages before exploring further.

# Get a wallet

> Fetch a single wallet you created, by its Minisend-assigned id.

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

## Endpoint

```text theme={null}
GET https://merchant.minisend.xyz/api/v1/wallets/{walletId}
```

```text theme={null}
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](/api-reference/wallet-api/create-wallet) instead: that call is create-or-get and returns the existing wallet.

## Example

```bash theme={null}
curl https://merchant.minisend.xyz/api/v1/wallets/3f6b2e1a-... \
  -H "Authorization: Bearer wsk_live_your_key_here"
```

## Response (200)

```json theme={null}
{
  "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](/api-reference/wallet-api/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 |