Cubewire LogoDeveloper
Support
Onboarding
Cubewire Developer Hub Logo
SOC 2 Compliant

Developer documentation and tools for Cubewire's digital wallet infrastructure. Built for developers, by developers.

developers@cubewire.com
TwitterGitHubDiscord

Developer Tools

  • API Documentation
  • API Reference

Resources

  • Documentation

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
© 2026 Cubewire. All rights reserved.
Developer Documentation Portal•Built with ♥ for developers
  1. Cubewire Wallet
  2. Manage Transactions
  3. Search transactions

Search transactions

Search for transactions using partial text matching across hashes, addresses, and workflow IDs. Returns up to 50 matching transactions. Use this when you have part of a hash or address but not the exact transaction ID.

Search Types

TypeDescription
allSearch across all fields (comprehensive, slower)
hashBlockchain transaction hash only
addressSender or recipient addresses
workflowIdTemporal workflow ID only

How Matching Works

Searches use partial text matching (case-insensitive). A transaction matches if the search query appears anywhere in the searched field.

Query Examples

Query TypeExample QueryWhat It Finds
Hash0x8fcAll transactions with hashes containing "0x8fc"
Address0x1234567890abTransactions where sender OR recipient contains this
Workflow IDtransaction-workflow-2024All workflow IDs containing "2024"

Response Fields

Returns a response object { data: [...] } containing an array of matching transactions with the same structure as the list endpoint:

FieldTypeDescription
idUUIDUnique transaction identifier
createdAtdatetimeTransaction creation timestamp (ISO 8601, UTC)
updatedAtdatetimeLast update timestamp (ISO 8601, UTC)
workflowIdstringWorkflow identifier for transaction orchestration
senderAddressstringSender blockchain address (0x...)
recipientAddressstringRecipient blockchain address (0x...)
valuestringTransaction value in smallest unit (wei for native; token base units for ERC-20)
assetstringAsset symbol (e.g., ETH, USDC)
networkstringBlockchain network name (e.g., Ethereum, Polygon)
organizationIdUUIDOwning organization ID
hashstringBlockchain transaction hash (nullable until submitted)
statusenumCurrent lifecycle status (see Status Values below)
failureReasonstringFailure description if status is FAILED (nullable)
gasLimitstringMaximum gas units allocated
gasPricestringGas price in wei (legacy transactions, nullable)
gasUsedstringActual gas consumed (after confirmation)
blockNumberstringBlock number where transaction was mined
contractAddressstringDeployed contract address (CONTRACT_DEPLOY only, nullable)
metadataobjectAdditional transaction metadata (see Metadata Fields)
auditLogsarrayComplete timeline of all transaction events

Use Cases

  • Find transactions when you only have part of a hash
  • Discover all transactions involving a specific address
  • Locate transactions by partial workflow ID from logs
  • Build search bars in transaction dashboards

Required Permission

transactions:read

On this page

  • Search Types
  • How Matching Works
  • Query Examples
  • Response Fields
  • Use Cases
  • Required Permission
  1. Cubewire Wallet
  2. Manage Transactions
  3. Search transactions

Search transactions

Search for transactions using partial text matching across hashes, addresses, and workflow IDs. Returns up to 50 matching transactions. Use this when you have part of a hash or address but not the exact transaction ID.

Search Types

TypeDescription
allSearch across all fields (comprehensive, slower)
hashBlockchain transaction hash only
addressSender or recipient addresses
workflowIdTemporal workflow ID only

How Matching Works

Searches use partial text matching (case-insensitive). A transaction matches if the search query appears anywhere in the searched field.

Query Examples

Query TypeExample QueryWhat It Finds
Hash0x8fcAll transactions with hashes containing "0x8fc"
Address0x1234567890abTransactions where sender OR recipient contains this
Workflow IDtransaction-workflow-2024All workflow IDs containing "2024"

Response Fields

Returns a response object { data: [...] } containing an array of matching transactions with the same structure as the list endpoint:

FieldTypeDescription
idUUIDUnique transaction identifier
createdAtdatetimeTransaction creation timestamp (ISO 8601, UTC)
updatedAtdatetimeLast update timestamp (ISO 8601, UTC)
workflowIdstringWorkflow identifier for transaction orchestration
senderAddressstringSender blockchain address (0x...)
recipientAddressstringRecipient blockchain address (0x...)
valuestringTransaction value in smallest unit (wei for native; token base units for ERC-20)
assetstringAsset symbol (e.g., ETH, USDC)
networkstringBlockchain network name (e.g., Ethereum, Polygon)
organizationIdUUIDOwning organization ID
hashstringBlockchain transaction hash (nullable until submitted)
statusenumCurrent lifecycle status (see Status Values below)
failureReasonstringFailure description if status is FAILED (nullable)
gasLimitstringMaximum gas units allocated
gasPricestringGas price in wei (legacy transactions, nullable)
gasUsedstringActual gas consumed (after confirmation)
blockNumberstringBlock number where transaction was mined
contractAddressstringDeployed contract address (CONTRACT_DEPLOY only, nullable)
metadataobjectAdditional transaction metadata (see Metadata Fields)
auditLogsarrayComplete timeline of all transaction events

Use Cases

  • Find transactions when you only have part of a hash
  • Discover all transactions involving a specific address
  • Locate transactions by partial workflow ID from logs
  • Build search bars in transaction dashboards

Required Permission

transactions:read

On this page

  • Search Types
  • How Matching Works
  • Query Examples
  • Response Fields
  • Use Cases
  • Required Permission