Get a Crypto Withdrawal
One crypto withdrawal created through v3, by id. Withdrawals created through v2 are not found here: read them through v2.
Part of crypto v3, in beta. This endpoint stays open after crypto v3 withdrawals are turned off, so a withdrawal already made can still be followed.
A workspace-scoped key reads any withdrawal of the workspace, or narrows to one account with account_id; an account-scoped key reads only its own account's, and another account's reads as 404.
New in v3: v2's crypto endpoints cannot read a withdrawal back.
Authorization:
Every request is signed with your API key: a short-lived JWT, signed with your private key, sent in one header on /v3/* and /api/v2/* alike.
Headers:
Authorization: APIKey {SIGNED_JWT}
How to build and sign the JWT: Authentication.
Endpoint
/v3/crypto/withdrawals/{withdrawal_id}
Path parameters
| Parameter | Type | Description |
|---|---|---|
withdrawal_id | string (wtx_…) | Required. The withdrawal. |
Query parameters
| Parameter | Type | Description |
|---|---|---|
account_id | string (cst_…) | Optional. Only find the withdrawal if it is this account's. |
Response Sample
{
"id": "wtx_01k9a1b3c5d7e9f1g3h5j7k9m1",
"account_id": "cst_01h455vb4pex5vsknk084sn02q",
"status": "success",
"coin": "USDC",
"amount": "250",
"fee": "10",
"total": "240",
"counterparty_id": "wlt_01k8z5q7r9s1t3v5w7x9y1z3a5",
"counterparty_address": "0x8f3b2c1d0e9a7b6c5d4e3f2a1b0c9d8e7f6a5b4c",
"reference": "inv-2026-10-0042",
"description": "Supplier payment",
"status_reason": "Completed by the custody provider",
"provider": "fireblocks",
"external_id": "7f3c1a2e-9b4d-4e8a-a1c2-5d6e7f8a9b0c",
"tx_hash": "0x9f1c2b3a4d5e6f708192a3b4c5d6e7f8091a2b3c4d5e6f708192a3b4c5d6e7f8",
"grace_ends_at": "2026-10-20T18:05:00Z",
"created_at": "2026-10-20T18:00:00Z",
"updated_at": "2026-10-20T18:11:37Z"
}
Response Schema
The withdrawal, with the fields described in Create a Crypto Withdrawal. Its statuses are in The life of a withdrawal.
Errors
| Status | message | When |
|---|---|---|
400 | failed to parse request | withdrawal_id is not a wtx_… id, or account_id is not a cst_… id. |
401 | unauthorized | Missing or invalid signature. |
403 | forbidden | An account-scoped key named another account. |
404 | withdrawal_not_found | No such withdrawal, it belongs to another account, or it was created through v2. |
Support and Resources
If you need assistance or have any questions, our support team is here to help. You can contact our support team at support@blockwyre.com.
Stay Updated
Stay up-to-date with the latest news, updates, and features from BlockWyre by following us on social media:
- Instagram: BlockWyre Instagram
- Twitter: BlockWyre Twitter
- Facebook: BlockWyre Facebook
- LinkedIn: BlockWyre LinkedIn
We are excited to have you on board and look forward to seeing how you leverage BlockWyre's powerful tools to enhance your financial operations. Happy integrating!