blockchain API: managed access to blockchain networks
Running your own blockchain node is an operational burden: client upgrades, fork monitoring, hundreds of gigabytes of state storage, on-call during incidents. blockchain API through Settla removes that burden — your team gets a stable endpoint with 99.9% SLA and stops spending engineering time on infrastructure.
What blockchain API delivers in practice
Settla's endpoint accepts the same JSON-RPC calls as a native node — no changes to business logic. Additionally available: batch requests (up to 100 methods per call), WebSocket subscriptions for real-time events, and archive data from the genesis block. All without maintaining your own infrastructure.
p95 latency below 50 ms is achieved through geo-distributed points of presence: requests are routed to the nearest node. If one data centre degrades, traffic switches automatically with no client-side changes.
| Parameter | Value |
|---|---|
| Availability | 99.9% SLA |
| Latency (p95) | <50 ms |
| Batch requests | up to 100 methods per call |
| WebSocket | real-time event subscriptions |
| Archive data | history from genesis block |
Supported networks
| Network | Type | Methods | WebSocket |
|---|---|---|---|
| Bitcoin | UTXO | getblock, sendrawtransaction, gettxout | ✓ |
| Ethereum | EVM | eth_call, eth_sendRawTransaction, eth_getLogs | ✓ |
| BNB Chain | EVM | Full EVM-compatible set | ✓ |
| Tron | TVM | getaccount, createtransaction, broadcasttransaction | ✓ |
| Solana | PoH | getTransaction, sendTransaction, getSlot | ✓ |
| Polygon | EVM | Full EVM-compatible set | ✓ |
Who uses blockchain API
- Crypto exchanges (CEX/DEX) — transaction broadcast, mempool monitoring
- Crypto wallets — balance sync, incoming transfer tracking
- DeFi protocols — smart contract state reads, event logs
- Crypto exchangers — transaction verification, confirmation status
- NFT marketplaces — minting, transfers, token metadata retrieval
Archive access is especially important for analytics and compliance: transaction history from the genesis block is available through the same endpoint with no additional configuration.
Integration: from key to first request
Register on Settla — get an API key — substitute the endpoint into your config. For most libraries (ethers.js, web3.py, bitcoin-rpc) it is enough to replace the provider URL. Documentation includes examples for Node.js, Python, Go, and cURL. A test environment lets you validate the integration without production load.
For high-throughput systems, dedicated nodes with private endpoints are available: no request limits, isolation from other clients, priority support. This is the optimal choice for exchanges, custodians, and any system with SLA requirements above the public tier.
Pricing and scaling
The public tier suits development and MVP: base request limit, one API key, archive access. As traffic grows, the tier scales without switching providers and without code changes — just increase the limit or move to a dedicated plan.
Enterprise clients get custom SLAs, dedicated nodes, and white-label options. Settla serves platforms handling over a million requests per day without latency degradation.
Get started with blockchain API on Settla
Register on Settla, get an API key, and make your first blockchain request — no infrastructure setup, no node maintenance, no 3 AM incidents from forks.
