---
title: "Get Withdrawal Instructions for Crypto"
method: GET
path: "/v1/wallets/withdrawal-instructions/crypto/{symbol}"
tags: ["custody"]
---

# Get Withdrawal Instructions for Crypto

`GET /v1/wallets/withdrawal-instructions/crypto/{symbol}`

## Request

- Base URL: `https://api.exchange.bullish.com/trading-api`
- URL: `https://api.exchange.bullish.com/trading-api/v1/wallets/withdrawal-instructions/crypto/{symbol}`
- Auth: HTTP bearer
- TypeScript: <https://skmtc.dev/bullish/apis/bullish-trading-api/docs/v1/wallets/withdrawal-instructions/crypto/:symbol/get.ts> (a function with typed inputs; its response is checked against the schema)

Get crypto withdrawal instructions, requires [bearer token](/rest/authentication#add-authenticated-request-header) in authorization header. Please note that all withdrawal addresses must be whitelisted via the Bullish website before any digital asset withdrawals can be processed.

Please note that Custody endpoints utilize a non-multiplied asset format for long decimal assets like SHIB and PEPE, ensuring consistency with real-world asset representation. This differs from Trading endpoints, which use a multiplied asset format, such as SHIB1M and PEPE1M. For more information, please see [help center](https://bullishexchange.atlassian.net/wiki/spaces/BHC/pages/20807684/Understanding+Multiplied+Assets+PEPE1M+and+SHIB1M)

**Ratelimited:** `True` - see [custody limits](/rest/general/rate-limits)

## Path parameters

- `symbol` string, required: symbol representing coin or token, e.g. USDC, BTC, ETH, SHIB

## Query parameters

- `signed` boolean: Whether this destination has been signed by the user. Some operations such as withdrawal requires the destination to be signed.
- `locked` boolean: Whether this destination is currently in a withdrawal lock period. Addresses are locked upon whitelisting for a 24-hour security period.

## Response `200`

OK

- CustodyCryptoWithdrawalInstructions[]
  - `network` string, required: the network of the native coin or token, e.g. BTC, ETH, SOL
  - `symbol` string, required: symbol representing coin or token, e.g. USDC, BTC, ETH, SHIB
  - `address` string, required: an address on the given network
  - `fee` string, required: withdrawal fee charged in units of symbol, not in smaller denominations (e.g. BTC not Satoshi, ETH not Wei)
  - `memo` string: memo or destination tag that will be used as a reference on transaction
  - `label` string, required: descriptive label of destination provided by user
  - `destinationId` string, required: destination id provided by bullish that uniquely identifies a whitelisted address or account
  - `vaspName` string: The name of the hosting VASP of the wallet. This is only applicable for `HOSTED` wallets.
  - `userWalletType` 'HOSTED' | 'SELF_HOSTED' | 'UNKNOWN', required: The host type of the wallet. `HOSTED` wallet uses a custodial wallet service, `SELF_HOSTED` wallet is a non-custodial wallet.
  - `signed` boolean, required: Whether this destination has been signed by the user. Some operations such as withdrawal requires the destination to be signed.
  - `locked` boolean: Whether this destination is currently in a withdrawal lock period. Addresses are locked upon whitelisting for a 24-hour security period.
  - `lockExpiryDateTime` string, date-time: ISO 8601 Zulu timestamp of when the withdrawal lock period expires. Applies only when `locked` is true.

## Other responses

- `429`: Too Many Requests
- `500`: Internal Server Error

---

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