Suggested order of work: pick an HTTP client, use the public base URLs in the API reference, then call the documented routes for your node class (mempool, storage, or miner).
Client tooling
Use any REST client, curl, or your application’s HTTP stack. Per-route request and response JSON is on each reference page. Code that ships with the project lives on GitHub.
Public base URLs (reference deployment)
Examples in the API reference use these HTTPS origins, one per node class. Paths in each section are always relative to the matching class—mempool calls use the mempool host, storage reads use the storage host, and so on. For a private, staging, or alternate network, swap in that deployment’s bases; the route names and JSON contracts stay the same as in the per-page documentation.
- Mempool —
https://mempool.lineage.to(transactions, balances, supply, mempool metadata) - Storage —
https://storage.lineage.to(blocks, chain entries, read-oriented history) - Miner —
https://miner.lineage.to(operator-facing HTTP where a release exposes it; a small surface compared to mempool and storage)
See the API overview for a short routing map and deep links into each section.
Verify you are talking to a node
Use small, read-only calls from the storage or mempool sections of the reference (for example, node metadata or health-style routes) to confirm connectivity before you send transactions. Follow the per-route contracts in the reference; the exact JSON shapes may evolve between releases, so always check the response body your deployment returns.
A minimal connectivity check is the fetch_balance or a read-only storage route. Each API reference page documents full request and response JSON, including the standard error envelope. The snippet below is only a loose sketch of how a high-level info payload might list route names; your node may differ.
{
"node_type": "Storage",
"node_api": [
"block_by_num",
"latest_block",
"blockchain_entry"
]
}Next steps
- API overview — choose mempool, storage, or miner.
- Concepts — understand how the pieces fit together.
- Mempool, storage, and miner references — from API overview and each endpoint page in the left navigation.