Get Outgoing Transaction Count: API Migration (v3 to v4)

This guide covers the migration from legacy v3 chain-specific Get outgoing transaction count endpoints to the new unified Blockchains API endpoint Get transaction count

Endpoint Change Summary

Component	v3 (Legacy)	v4 (New)
Standard Pattern	`/v3/{chain}/transaction/count`	`/v4/data/blockchains/transaction/count`
Address Pattern	`/v3/{chain}/transaction/count/{address}`	`/v4/data/blockchains/transaction/count`

Deprecated v3 Endpoints

The following chain-specific endpoints have been consolidated:

Old v3 Endpoint	Status
`/v3/arb/transaction/count/{address}`	Deprecated
`/v3/avalanche/transaction/count`	Deprecated
`/v3/base/transaction/count`	Deprecated
`/v3/bsc/transaction/count`	Deprecated
`/v3/celo/transaction/count`	Deprecated
`/v3/cronos/transaction/count`	Deprecated
`/v3/egld/transaction/count`	Deprecated
`/v3/ethereum/transaction/count`	Deprecated
`/v3/fantom/transaction/count`	Deprecated
`/v3/flare/transaction/count`	Deprecated
`/v3/kcs/transaction/count`	Deprecated
`/v3/klaytn/transaction/count`	Deprecated
`/v3/one/transaction/count`	Deprecated
`/v3/optimism/transaction/count`	Deprecated
`/v3/polygon/transaction/count`	Deprecated
`/v3/sonic/transaction/count/{address}`	Deprecated
`/v3/xdc/transaction/count`	Deprecated

Migration Steps

1. Update Your Base URL

Standard endpoints:

- GET /v3/ethereum/transaction/count
+ GET /v4/data/blockchains/transaction/count?chain=ethereum-mainnet&address={address}

2. Adjust Chain Identifiers

Ensure you're using the new chain identifier format (e.g., ethereum-mainnet instead of ethereum).

3. Update Response Handling

Review your code for any response schema changes between v3 and v4.

🚧
Attention
Mind potential breaking changes.