API Overview
Radix exposes four APIs at different abstraction levels. Most developers only need the Gateway API.
| API | Purpose | Best For | Access |
|---|---|---|---|
| Gateway | High-level ledger queries and transaction submission | dApps, wallets, explorers | Public endpoints |
| Core | Low-level transaction and state data from nodes | Exchanges, analytics, integrators | Private / self-hosted |
| Engine State | Complete current ledger state at engine level | Advanced state queries | Self-hosted (requires node config) |
| System | Node health and diagnostics | Node operators | Local only |
Gateway API
The Gateway API is the primary interface for dApp developers. It provides entity state queries, transaction submission, stream queries, and historical state access — all via JSON POST requests with cursor-based pagination.
Official Endpoints
| Network | URL |
|---|---|
| Mainnet | https://mainnet.radixdlt.com |
| Stokenet | https://stokenet.radixdlt.com |
These are rate-limited by IP. For production dApps, use a third-party provider or run your own Gateway.
Key Endpoint Groups
/state/*— entity details, resource balances, metadata, vault contents/transaction/*— submit, preview, and check transaction status/stream/transactions— query committed transactions with filters/status/gateway-status— current ledger state version and epoch
Use the Gateway SDK (@radixdlt/babylon-gateway-api-sdk) for typed TypeScript access.
Core API
The Core API gives direct access to a node's view of the ledger — transaction-level detail, raw state, and streaming committed transactions. It includes an LTS (Long-Term Support) sub-API designed for exchange integrators.
LTS Endpoints
/lts/transaction/submit— submit a notarized transaction/lts/transaction/status— check transaction status by intent hash/lts/state/account-all-fungible-resource-balances— all token balances for an account/lts/transaction/construction— get current epoch for building transactions
The Core API requires running your own node. Third-party providers include Grove (free tier: 5M requests/day) and NowNodes.
Engine State and System APIs
Engine State API
Provides complete current state at the Radix Engine abstraction level. More comprehensive than Core API state queries but requires explicit node configuration (available since node v1.1.3.1). Useful for advanced state inspection without running a full Gateway.
System API
Node diagnostics only — health checks, connection info, performance metrics. Used for monitoring, not application development.
Which API Should I Use?
| Use Case | API |
|---|---|
| Frontend dApp reading account state | Gateway SDK |
| Submitting transactions from dApp | Gateway (via dApp Toolkit) |
| Exchange integration (deposits, withdrawals) | Core API (LTS endpoints) |
| Indexing / analytics pipeline | Core API (streaming) |
| Node health monitoring | System API |
