The New Era of Tatum Multichain Data APIs

At Tatum, our goal has always been to simplify how developers work with blockchains. As more teams move toward multichain architectures, one challenge keeps coming up consistently: managing the operational complexity that comes with it.

For solo developers and enterprise teams alike, supporting multiple chains often means maintaining dozens, sometimes hundreds, endpoints. Each blockchain has its own response format, structure, pagination logic, and edge cases. Adding a new network rarely means just switching a configuration; it usually requires writing and maintaining additional parsing logic.

With this update to our v4 Data API, we’re addressing that problem directly by unifying how blockchain data is delivered across networks.

Why the Move to Unified Data?

The Blockchains API simplifies this by providing:

• Unified multi-chain interface for querying blockchain data
• Enriched data in compare to standard raw RPC data
• Standardized response format across supported blockchains
• Direct access to raw blockchain data including blocks and transactions
• Scalable infrastructure designed for high-volume data queries

In our legacy v3 structure, developers interacted with more than 175 network-specific API endpoints. While this approach offered flexibility, it also created a growing maintenance burden. Supporting multiple chains meant adapting to different schemas and handling inconsistencies between EVM and non‑EVM networks.

That overhead adds up over time. Backend services become tightly coupled to chain-specific logic. Expanding to a new blockchain requires additional development, testing, and long-term maintenance.

The v4 Data API replaces that fragmented structure with a standardized abstraction layer. Instead of adjusting your application logic for each chain, you interact with a consistent response format regardless of the underlying network. Whether the data comes from an EVM chain, Bitcoin, or Zcash, the structure remains predictable.

This shift reduces the amount of custom transformation code required and makes multichain support significantly easier to scale.

Another important change is pricing standardization. Infrastructure planning becomes more straightforward when costs are predictable across supported networks. Teams can expand into new ecosystems without having to re-evaluate pricing models for each chain individually.

From a long-term perspective, this unified architecture also enables faster chain integrations and feature rollouts. By standardizing internally, we can extend support to additional networks without introducing new inconsistencies to developers.

What’s New: Expanded Chain Coverage

Alongside the structural update, we’ve extended the v4 standard to several highly requested networks.

Developers can now access unified data endpoints for high-performance chains such as Monad (Mainnet and Testnet), Berachain (Mainnet and Testnet), and Unichain (Mainnet and Sepolia). We’ve also expanded coverage to widely used ecosystems including Chiliz, EOS, Ethereum Classic, and Bitcoin Cash. In addition, privacy-focused and legacy networks such as Zcash (Mainnet and Testnet) and Litecoin Testnet are now available within the same standardized framework.

For teams building wallets, DeFi applications, analytics platforms, or payment systems, this means expanding to these chains no longer requires reworking your data handling logic. The integration process remains consistent across networks.

The goal of this release is not to introduce new complexity, but to remove it. Multichain development should not require maintaining parallel infrastructure paths for each blockchain. With the unified v4 Data API, adding support for another network becomes an incremental step rather than a structural rewrite.

If you’re currently operating on v3 and planning to expand your multichain coverage, this update is designed to reduce the operational overhead involved in that transition.

You can explore the full list of updates regarding our v4 endpoints here, as well as all other new features and improvements in our detailed changelog.

The New Unified Blockchains API (v4)

The shift is simple. Instead of chain-specific paths, you now use a unified structure.

Migration Roadmap: What You Need to Know

To provide the best possible service, we will eventually be sunsetting our legacy v3 endpoints for blocks, balances, and transactions. We want to ensure this transition is as smooth as possible for our community of over 300+ Paygo and Enterprise users.

Please mark these key dates in your calendar:

March 7th, 2026: Legacy v3 documentation will be removed from our public docs.‍

May 31st, 2026 (Soft EOL): Support for legacy endpoints begins to wind down. We recommend all users complete their migration by this date.

June 30th, 2026 (Hard Pull the Plug): Legacy v3 endpoints will be officially decommissioned.

Beyond just avoiding the sunset date, moving to v4 now gives you immediate access to our newest chain support (like Berachain and Monad) and the improved reliability of our v4 infrastructure.

We’re Here to Help!

We understand that migrating infrastructure takes time. Our team is committed to making this transition easy. We will be providing detailed mapping guides to help you swap your current v3 calls for their v4 equivalents.

If you have questions or need assistance with the migration, please visit our troubleshooting section or reach out to support via your dashboard.

The future of Web3 is multichain, but it doesn't have to be complicated. Welcome to the new era of Tatum Data APIs!