Skip to content

Transaction origin and destination filters, and balance filtering

The Wallet-as-a-Service API adds filters for transaction and wallet balance lists, retry-safe freeze requests, and a policy matcher for all counterparties.

What changed

  • Origin and destination transaction filters. filter.origin.* and filter.destination.* match the origin or destination of a transaction by address, wallet or address ID, or counterparty ID. Wallet-as-a-Service deprecates the address-only filter.originAddress.* and filter.destinationAddress.* filters. See Filter transactions by origin or destination.
  • Wallet balance filters, search, and pagination. GET /v2/vaults/{vaultId}/wallets/{walletId}/balances accepts blockchain, contract, symbol, and asset standard filters, a search parameter, and pagination. aggregatedFiatValue covers the complete filtered result, and each asset includes a displaySymbol field. See Filter, search, and page balances.
  • Retry-safe freeze and unfreeze. Freeze and unfreeze requests accept an optional mutationId. The freezeInfo object reports the authority, mutationId, and freezeRevision of each freeze state change. See Freeze and unfreeze transactions.
  • ALL_COUNTERPARTIES policy matcher. The matcher applies a policy to every transaction whose destination resolves to a counterparty. See ALL_COUNTERPARTIES.
  • Automated market maker (AMM) Withdraw validation. AMM Withdraw requires lpTokenIn and flags, and Wallet-as-a-Service accepts only the WITHDRAW_LP_TOKEN and WITHDRAW_ONE_ASSET_LP_TOKEN request shapes. See XRP Ledger AMM APIs.

References