List Crypto Deposits

The coins received by the workspace or by one account, newest first. Deposits recorded through v2 are listed too: they are the same records.

Beta

Part of crypto v3, in beta. This endpoint is open whether or not crypto v3 is enabled for the workspace.

A workspace-scoped key lists every deposit in the workspace, or one account's with account_id; an account-scoped key lists its own account's.

New in v3: v2 lists crypto deposits only among all transactions, in List Transactions.

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

GET

/v3/crypto/deposits

Query parameters

Parameter	Type	Description
account_id	string (cst_…)	Only this account's deposits. An account-scoped key may omit it; naming another account is refused.
wallet_id	string (wlt_…)	Only the deposits that landed on this wallet.
coin	string	Only deposits of this coin, for example USDC. Any casing.
status	string	Only deposits in this status: pending, processing, success or failed.
created_at_gte	string (date-time)	Created at or after this time. RFC 3339, or a date (2026-10-01) for midnight UTC at its start.
created_at_lt	string (date-time)	Created before this time, in the same forms.
page	integer	Page number, from 1. Default 1.
limit	integer	Rows per page. Default 25, at most 100.

Response Sample

{
  "data": [
    {
      "id": "wtx_01k9b2c4d6e8f0g2h4j6k8m0n2",
      "account_id": "cst_01h455vb4pex5vsknk084sn02q",
      "wallet_id": "wlt_01k8y4p6q8r0s2t4v6w8x0y2z4",
      "status": "success",
      "coin": "USDC",
      "amount": "100",
      "fee": "1.5",
      "total": "98.5",
      "address": "0x2c4e6a8b0d1f3a5c7e9b1d3f5a7c9e1b3d5f7a9c",
      "tx_hash": "0x5e7a9c1b3d5f7a9c1e3b5d7f9a1c3e5b7d9f1a3c5e7b9d1f3a5c7e9b1d3f5a7c",
      "provider": "fireblocks",
      "external_id": "0b1c2d3e-4f5a-4b6c-8d7e-9f0a1b2c3d4e",
      "created_at": "2026-10-20T15:12:44Z",
      "updated_at": "2026-10-20T15:14:02Z"
    }
  ],
  "page": 1,
  "limit": 25,
  "total_items": 1,
  "total_pages": 1
}

Response Schema

Field	Type	Description
data	array	The deposits on this page.
data[].id	string (wtx_…)	The deposit. v2's transaction id, as a TypeID.
data[].account_id	string (cst_…)	The account it was credited to.
data[].wallet_id	string (wlt_…)	The wallet it landed on. Absent when the coins were sent to an address the account was never given; the deposit is still the account's.
data[].status	string	pending: seen on the network, not credited yet. processing: a deposit recorded through v2 that is not credited yet. success: credited. failed: never credited.
data[].coin	string	The coin, upper case.
data[].amount	string (decimal)	What arrived.
data[].fee	string (decimal)	What the platform kept.
data[].total	string (decimal)	What the account was credited: amount minus fee.
data[].address	string	The address it was sent to.
data[].tx_hash	string	The network transaction hash. Absent until the network has it.
data[].provider	string	The custodian that received it.
data[].external_id	string	The custodian's id for the transfer.
data[].created_at / updated_at	string (date-time)	RFC 3339, UTC.
page, limit, total_items, total_pages	integer	Pagination, as described in the API v3 overview. next_cursor and prev_cursor are not returned yet.

Amounts are decimal strings in the coin, without trailing zeros (see Amounts).

Errors

Status	message	When
400	failed to parse request	A parameter has the wrong form: page or limit is not an integer, coin is not a ticker, status is not one of the listed values, account_id is not a cst_… id, wallet_id is not a wlt_… id, or a date is neither RFC 3339 nor YYYY-MM-DD.
401	unauthorized	Missing or invalid signature.
403	forbidden	An account-scoped key named another account.

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!