Transaction Endpoints
Transaction API
Operation Identity:- Operation ID:
getTransaction GET /v1/{chainName}/transaction_v2/{txHash}/- SDK:
TransactionService.getTransaction()
Path Parameters
Query Parameters
Response Fields
Item Fields
Credit Cost: 0.1 per call
Processing: Realtime
Tip: Estimate your monthly cost for this API using the Pricing Calculator.
Note: Base cost isCalls with0.1credits (e.g. requests that return with status200but no items).
no-logs cost 0.05 credits/item.
Internal transactions are included in the response by using with-internal and cost 0.05 credits/item.
Note: with-internal is supported on select EVM chains only. See Traces Support for the current list of supported chains.
Related guides
Comparing GoldRush’s Transactions API to RPC Providers How to Get Transaction History for an Address on EthereumBlock Transactions API by Page
Operation Identity:- Operation ID:
getTransactionsForBlockByPage GET /v1/{chainName}/block/{blockHeight}/transactions_v3/page/{page}/
Path Parameters
Query Parameters
Response Fields
Link Fields
Item Fields
Credit Cost: 0.1 per item
Processing: Realtime
Tip: Estimate your monthly cost for this API using the Pricing Calculator.
Note: Requests that return statusEnabling200and no data cost0.1credits.
no-logs reduces request cost to 0.05 credits/item.
Block Transactions API
Operation Identity:- Operation ID:
getTransactionsForBlockHash GET /v1/{chainName}/block_hash/{blockHash}/transactions_v3/
Path Parameters
Query Parameters
Response Fields
Item Fields
Credit Cost: 0.1 per item
Processing: Realtime
Tip: Estimate your monthly cost for this API using the Pricing Calculator.
Note: Requests that return statusEnabling200and no data cost0.1credits.
no-logs reduces request cost to 0.05 credits/item.
Related guides
Introducing Transactions V3 APIs Comparing GoldRush’s Transactions API to RPC Providers How to Track Wallets or Transactions with the GoldRush API How to Get the Number of Transactions in a Block How to Get All Historical Transactions in a BlockEarliest Wallet Transactions API
Operation Identity:- Operation ID:
getEarliestTimeBucketTransactionsForAddress GET /v1/{chainName}/bulk/transactions/{walletAddress}/
Path Parameters
Query Parameters
Response Fields
Link Fields
Item Fields
Credit Cost: 0.1 per item
Processing: Realtime
Tip: Estimate your monthly cost for this API using the Pricing Calculator.
Note: Returns the same results as the first timebucket for an address in the Get recent transactions endpoint.Requests that return status
200 and no data cost 0.1 credits.
Calls with no-logs cost 0.05 credits/item.
Internal transactions are included in the response by using with-internal and cost 0.05 credits/item.
Note: with-internal is supported on select EVM chains only. See Traces Support for the current list of supported chains.
Related guides
Introducing Transactions V3 APIs Comparing GoldRush’s Transactions API to RPC Providers How to Get Transaction History for an Address on EthereumPaginated Wallet Transactions API
Operation Identity:- Operation ID:
getTransactionsForAddressV3 GET /v1/{chainName}/address/{walletAddress}/transactions_v3/page/{page}/
Path Parameters
Query Parameters
Response Fields
Link Fields
Item Fields
Credit Cost: 0.1 per item
Processing: Realtime
Tip: Estimate your monthly cost for this API using the Pricing Calculator.
Note: This endpoint returns paginated transactions, starting with the earliest transactions on page 0. For the most recent transactions, refer to the Get recent transactions for address (v3) endpoint.Requests that return status
200 and no data cost 0.1 credits.
Enabling no-logs reduces request cost to 0.05 credits/item.
Internal transactions are included in the response by using with-internal and cost 0.05 credits/item.
Note: with-internal is supported on select EVM chains only. See Traces Support for the current list of supported chains.
Related guides
Introducing Transactions V3 APIs Comparing GoldRush’s Transactions API to RPC Providers How to Get Transaction History for an Address on EthereumWallet Transaction History API
Operation Identity:- Operation ID:
getRecentTransactionsForAddress GET /v1/{chainName}/address/{walletAddress}/transactions_v3/
Path Parameters
Query Parameters
Response Fields
Link Fields
Item Fields
Credit Cost: 0.1 per item
Processing: Realtime
Tip: Estimate your monthly cost for this API using the Pricing Calculator.
Note: Requests that return statusEnabling200and no data cost0.1credits.
no-logs reduces request cost to 0.05 credits/item.
Internal transactions are included in the response by using with-internal and cost 0.05 credits/item.
Note: with-internal is supported on select EVM chains only. See Traces Support for the current list of supported chains.
Related guides
Introducing Transactions V3 APIs Comparing GoldRush’s Transactions API to RPC ProvidersTime Bucket Transactions API
Operation Identity:- Operation ID:
getTimeBucketTransactionsForAddress GET /v1/{chainName}/bulk/transactions/{walletAddress}/{timeBucket}/- SDK:
TransactionService.getTimeBucketTransactionsForAddress()
Path Parameters
Query Parameters
Response Fields
Link Fields
Item Fields
Credit Cost: 0.1 per item
Processing: Realtime
Tip: Estimate your monthly cost for this API using the Pricing Calculator.
Note: Requests that return statusEnabling200and no data cost0.1credits.
no-logs reduces request cost to 0.05 credits/item.
Related guides
Scaling Transactions API with Time Buckets Introducing Transactions V3 APIs Comparing GoldRush’s Transactions API to RPC ProvidersWallet Transaction Summary API
Operation Identity:- Operation ID:
getTransactionSummary GET /v1/{chainName}/address/{walletAddress}/transactions_summary/- SDK:
TransactionService.getTransactionSummary()
Path Parameters
Query Parameters
Response Fields
Item Fields
Credit Cost: 1 per call
Processing: Batch
Tip: Estimate your monthly cost for this API using the Pricing Calculator.
Note: - Base cost is 1 credit.
- Using
with-gasis an additional1credit. - Using
with-transfer-countis an additional3credits.
Related guides
Building Web3 Wallets (Part 7) - Multi-Chain Wallet Activity Summary Comparing GoldRush’s Transactions API to RPC Providers How to Get Transaction History for an Address on EthereumBitcoin Transaction History API
Operation Identity:- Operation ID:
getTransactionsForBtcAddress GET /v1/cq/covalent/app/bitcoin/transactions/- SDK:
BitcoinService.getTransactionsForBtcAddress()
Query Parameters
Response Fields
Item Fields
Pagination Fields
Credit Cost: 0.1 per item
Processing: Realtime
Tip: Estimate your monthly cost for this API using the Pricing Calculator.
Note: Only supports non-HD bitcoin addresses.
Transaction Classification (with-classification)
Pass with-classification=true to identify the action behind each transaction - a swap, a token transfer, a liquidity deposit - instead of reconstructing intent from raw logs and transfers.
It costs an extra 0.05 credits per transaction returned, on top of the endpoint’s own cost. It is available on these endpoints, documented above:
- Transaction API
- Wallet Transaction History API
- Paginated Wallet Transactions API
- Time Bucket Transactions API
- Earliest Wallet Transactions API
- Block Transactions API by Page
- Block Transactions API
Perspective: which wallet the transaction is classified for
The same transaction reads differently depending on whose side you are on. On the wallet endpoints, each transaction is classified for the wallet address in the path. On the single-transaction endpoint there is no wallet in the path, so it takes anaccount-address parameter to choose the perspective. If you omit account-address, the transaction is classified from the sender’s point of view (from_address), which is often not the wallet you care about.
The classification object
Returned per transaction, only when with-classification=true.
Note:typeandcategoryvalues are lowersnake_case(eg:send_token, notsendToken).
Categories
Supported chains (23)
Classification is supported on the same chains aswith-internal:
Chain support changes over time. Check
is_tx_classification_supported on https://api.covalenthq.com/v1/chains/ for the current list rather than relying on this table.