Reliable and Fast Binance BNB Smart Chain RPCs and Data APIs
Access Tatum RPC Nodes for BNB Smart Chain with failovers, geo-balancing, and everything else you need to power apps reliably.
"Tatum helps us build robust product solutions in a fraction of the time."
Zac Barron
Product Lead at Binance
RPC Gateway
Connect to BNB Smart Chain's high-performance RPC Gateway to make your first calls, deploy and interact with smart contracts, estimate gas fees, and more.
Tatum RPC gateways are globally load balanced with automatic failovers and smart caching, so your applications stay fast and available even during traffic spikes.
With the BYO-RPC feature, you can plug in your own nodes alongside Tatum endpoints and centrally manage routing, prioritization, and failover policies across all RPC traffic.
Data API
Access a standardized API to retrieve token balances for a wallet on BNB Smart Chain, get transaction history, including internal transfers, and more.
Check exchange rates for tokens and fiat currencies on BNB Smart Chain or even verify malicious addresses.
Notifications
Receive webhook notifications for any event on Binance Smart Chain and monitor all smart contract events with multiple automatic retries, so you never miss critical on-chain activity while keeping notification costs extremely low.
Discover transaction events for Binance Smart Chain wallet addresses in the same stream to power dashboards, risk engines, and alerts.
Why Developers Build With Tatum
Zac Barron
Product Lead at Binance
David Spitzer-Dulagan
CTO at Limewire
Meni Cherbakovsky
VP Engineering at Zengo
Frequently Asked Questions
Connect to Tatum's BNB Smart Chain RPC Gateway using the endpoint format: bsc-mainnet.gateway.tatum.io or bsc-testnet.gateway.tatum.io.
Tatum's RPC Gateway provides discovery endpoints to help you explore available functionality:
/llms.txt: Access AI context and documentation for the network/_methods: Discover all supported interfaces and RPC methods for the network
Credits are consumed based on the complexity and resource requirements of each RPC method:
- 2 credits are consumed for Standard RPC methods (most common operations)
- 5 credits are consumed for the
eth_callmethod - 50 credits are consumed for Debug and Trace methods
When using the Tatum REST API or SDK, you need to authenticate yourself with an API key. Access Tatum services by authenticating with your API key using one of the following methods:
- X-API-Key in header (Recommended): Pass your API key in the
x-api-keyheader - Authorization Header (Bearer): Use
authorization: bearer {YOUR_API_KEY} - Authorization Header (Basic): Use HTTP Basic Authentication
For detailed authentication instructions and best practices, see the Authentication & Security documentation.
Get your API key by signing up at the Tatum Dashboard. Each free account includes two API keys – one for Mainnet and one for Testnet.
%20(15).jpg)
