Use This When
| Need | Endpoint family |
|---|---|
| Read account, ESDT, NFT, guardian, or storage data | /address/* |
| Send, simulate, cost, or track a transaction | /transaction/* |
| Read network config, economics, staking, token, or epoch data | /network/* |
| Read blocks, hyperblocks, or altered accounts | /block/*, /blocks/*, /hyperblock/* |
| Execute smart contract view calls | /vm-values/* |
Do Not Use This When
| Need | Use instead |
|---|---|
| You need direct P2P transaction propagation | Relayer broadcast |
| You need WebSocket event streams | Relayer |
| You need swap route construction | Aggregator |
Base URL
data, error, and code fields.
Flow
Call the compatible path
Use either root paths such as
/address/{address} or Go proxy-compatible /v1.0/... paths when migrating existing code.Let the Gateway route
Address-based requests are routed from the bech32 public key. Metachain requests use shard ID
4294967295.Check the response body
A
200 HTTP response can still contain a non-empty error field from the observer. Validate both HTTP status and body fields.Limits And Behavior
| Area | Behavior |
|---|---|
| OpenAPI coverage | 80 endpoints |
| Shard routing | Address-derived for account and transaction paths |
| Metachain routing | Shard ID 4294967295 |
| Compatibility | Root paths and /v1.0/ paths |
| Caching | Short TTLs on selected block, hyperblock, heartbeat, validator, and economics responses |
| Deduplication | Identical concurrent requests can share one observer call |
Next Steps
Quickstart
Query an account, simulate a transaction, and inspect the response.
Shard routing
How addresses, metachain requests, and fan-out endpoints are routed.
Caching and deduplication
Which calls are cached or coalesced, and how that affects freshness.
API reference
OpenAPI pages for all Gateway endpoint shapes.