List hot wallets, optionally filtered or searched by payment source, type and free text. (read access required)
Changed onLists hot wallets across payment sources with cursor-based pagination. searchQuery applies before pagination, so a wallet beyond the first page is still found.
Request
- Base URL: ./../api/v1/ (relative, and the document was published on a file host, not at the API’s origin)
- URL: ./../api/v1/wallet/list
- Auth: API key in header token
Query parameters
The number of wallets to return
Used to paginate through the wallets (provide the id of the last returned wallet)
Filter wallets to a single payment source
Filter wallets by type (Selling, Purchasing or Funding)
Filter to the single wallet with this payment key hash
Filter to wallets with this Cardano address
Free-text search applied before pagination, so a wallet beyond the first page is still found. Matches wallet address, collection address, note, payment key hash and id (case-insensitive substring), and the wallet type by either its API name ("Purchasing") or the label the admin UI renders ("Buying"). "%" and "_" are matched literally. Balance is not searchable: it is read from the chain, not stored. Combined with the exact filters above as a logical AND.
Response
Paginated list of hot wallets
Example response
{
"status": "success",
"data": {
"Wallets": [
{
"id": "unique_cuid_v2_auto_generated",
"paymentSourceId": "unique_cuid_v2_of_payment_source",
"type": "Selling",
"walletVkey": "wallet_vkey",
"walletAddress": "wallet_address",
"collectionAddress": null,
"note": "note",
"LowBalanceSummary": {
"isLow": false,
"lowRuleCount": 0,
"lastCheckedAt": "1970-01-20T20:00:36.260Z"
}
}
]
}
}Changes
- info
added the new optional
queryrequest parametersearchQuery
- info
- warning
deleted the
queryrequest parametersearchQuery
- warning