Solana API
Solana endpoints use Solana JSON-RPC method names. They do not support EVM methods such as eth_getProof, trace_block, or debug_traceCall.
Endpoint
| Item | Value |
|---|---|
| Network | Solana Mainnet |
| Protocol | Solana JSON-RPC |
| Chain identifier | solana-mainnet |
| Public HTTPS | https://solana-rpc.blockreq.com/v1/rpc/public |
| Private HTTPS | https://solana-rpc.blockreq.com/v1/rpc/BRQ1P0000000000000000000000000000000000000000000000000000 |
| WSS | wss://solana-rpc.blockreq.com/v1/rpc/BRQ1P0000000000000000000000000000000000000000000000000000 when enabled |
Core Methods
| Category | Methods |
|---|---|
| Health and version | getHealth, getVersion |
| Slot and epoch | getSlot, getBlockHeight, getEpochInfo |
| Blocks and transactions | getBlock, getTransaction, getLatestBlockhash when enabled by provider route |
| Subscriptions | slotSubscribe, logsSubscribe, signatureSubscribe over WSS when enabled |
Example
curl -X POST https://solana-rpc.blockreq.com/v1/rpc/public \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","method":"getBlockHeight","params":[],"id":1}'History Notes
Solana history access depends on the provider lane and method. Use Solana-native methods such as getBlock and getTransaction; EVM archive-state methods (eth_getProof, old-block eth_call, trace_*, debug_*) are not valid on Solana.