Solana RPC for your application

Start with the questions your app needs answered

A wallet needs balances. A payment screen needs transaction status. An indexer needs a way to fill missing records. JSON-RPC gives each of these workflows an explicit request and response, while WebSocket subscriptions provide ongoing notifications.

Keep RPC in your architecture even when you add a streaming feed. It is useful for initial state, user-driven lookups, and checking observations against the commitment level your application requires.

Connect through your Lumios dashboard

Open Endpoints, choose your available access, network, and location, then create a location token. Copy the HTTPS RPC URL shown for that location. Product availability and limits depend on your selected access.

Make a small read request before adding your application workload. This JSON body requests a recent blockhash at confirmed commitment; send it to the endpoint copied from your account.

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "getLatestBlockhash",
  "params": [{ "commitment": "confirmed" }]
}

Design for a complete request lifecycle

An accepted submission is the beginning of transaction tracking. Show a pending state, inspect execution errors, and update the interface when the required confirmation level is reached.

• Keep credential-bearing URLs on your server and redact them from error reports.
• Track request errors and tail latency by method, region, and workload.
• Budget retries so an outage cannot multiply your traffic without a limit.
• Choose historical retention, throughput, and locations based on the access shown in your account.

Common questions