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. Get transactions by vault address

Get transactions by vault address

Retrieve all transactions where a specific vault is either the sender or recipient. The vault address must belong to your organization. Supports all standard filtering, sorting, and pagination parameters.

Path Parameters

ParameterTypeRequiredDescription
vaultAddressstringYesBlockchain address (0x..., 42 characters)

Query Parameters

ParameterTypeDescription
pagenumberPage number for pagination
limitnumberItems per page (1-100)
statusstringFilter by status
assetstringFilter by asset symbol
networkstringFilter by network name
fromAddressstringFilter by sender address
toAddressstringFilter by recipient address
workflowIdstringFilter by Temporal workflow identifier
userIdstringFilter by user ID
organizationIdstringFilter by organization ID
startDatestringFilter by start date (ISO 8601)
endDatestringFilter by end date (ISO 8601)
sortBystringSort field (createdAt, updatedAt, timestamp, or value)
sortOrderstringSort order: asc or desc

Response Fields

The response is wrapped in an envelope: data contains the array of transactions and pagination contains paging metadata. Each transaction includes the same fields as the list transactions 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 human-readable format
assetstringAsset symbol (e.g., ETH, USDC)
networkstringNetwork chain ID as string
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 Gwei (legacy transactions, nullable)
gasUsedstringActual gas consumed (after confirmation)
blockNumberstringBlock number where transaction was mined
contractAddressstringDeployed contract address for contract deployments (nullable)
metadataobjectAdditional transaction metadata (see Metadata Fields)
auditLogsarrayComplete timeline of all transaction events

Use Cases

  • Display transaction history for a specific vault
  • Build vault detail pages with transaction lists
  • Generate vault-specific financial reports
  • Track all activity for compliance audits
  • Monitor incoming and outgoing transactions per vault

Required Permission

transactions:read

On this page

  • Path Parameters
  • Query Parameters
  • Response Fields
  • Use Cases
  • Required Permission
  1. Cubewire Wallet
  2. Manage Transactions
  3. Get transactions by vault address

Get transactions by vault address

Retrieve all transactions where a specific vault is either the sender or recipient. The vault address must belong to your organization. Supports all standard filtering, sorting, and pagination parameters.

Path Parameters

ParameterTypeRequiredDescription
vaultAddressstringYesBlockchain address (0x..., 42 characters)

Query Parameters

ParameterTypeDescription
pagenumberPage number for pagination
limitnumberItems per page (1-100)
statusstringFilter by status
assetstringFilter by asset symbol
networkstringFilter by network name
fromAddressstringFilter by sender address
toAddressstringFilter by recipient address
workflowIdstringFilter by Temporal workflow identifier
userIdstringFilter by user ID
organizationIdstringFilter by organization ID
startDatestringFilter by start date (ISO 8601)
endDatestringFilter by end date (ISO 8601)
sortBystringSort field (createdAt, updatedAt, timestamp, or value)
sortOrderstringSort order: asc or desc

Response Fields

The response is wrapped in an envelope: data contains the array of transactions and pagination contains paging metadata. Each transaction includes the same fields as the list transactions 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 human-readable format
assetstringAsset symbol (e.g., ETH, USDC)
networkstringNetwork chain ID as string
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 Gwei (legacy transactions, nullable)
gasUsedstringActual gas consumed (after confirmation)
blockNumberstringBlock number where transaction was mined
contractAddressstringDeployed contract address for contract deployments (nullable)
metadataobjectAdditional transaction metadata (see Metadata Fields)
auditLogsarrayComplete timeline of all transaction events

Use Cases

  • Display transaction history for a specific vault
  • Build vault detail pages with transaction lists
  • Generate vault-specific financial reports
  • Track all activity for compliance audits
  • Monitor incoming and outgoing transactions per vault

Required Permission

transactions:read

On this page

  • Path Parameters
  • Query Parameters
  • Response Fields
  • Use Cases
  • Required Permission