Interact with Solana nodes using JSON-RPC 2.0
OrbitFlare RPC nodes accept HTTP requests using the JSON-RPC 2.0 specification. This API allows you to interact with the Solana blockchain for querying data and submitting transactions.
To make a JSON-RPC request, send an HTTP POST request with the following specifications:
https://rpc.orbitflare.com
Content-Type: application/json
Field | Type | Description |
---|---|---|
jsonrpc | string | Must be “2.0” |
id | string/number | Unique request identifier |
method | string | The RPC method name |
params | array | Array of method parameters |
Responses will be JSON objects containing:
Field | Type | Description |
---|---|---|
jsonrpc | string | Always “2.0” |
id | string/number | Matches request identifier |
result | varies | The method’s result data |
error | object | Error details (if applicable) |
Many methods accept a commitment
parameter to specify how confirmed the data should be:
processed
: Latest block (fastest, not confirmed)confirmed
: Confirmed by supermajority (balance between speed and finality)finalized
: Finalized by supermajority (slowest, fully confirmed)Example with commitment:
You can send multiple requests in a single HTTP call by providing an array of request objects:
Type | Description |
---|---|
Pubkey | Base-58 encoded public key string |
Hash | Base-58 encoded SHA-256 hash string |
Signature | Base-58 encoded Ed25519 signature |
Slot | Integer block height/slot number |
You can check node health with a GET request:
Possible responses:
ok
: Node is healthy and up-to-datebehind { slots: number }
: Node is behind by N slotserror
: Node is unhealthyRate limits vary by subscription tier. Check your dashboard for your current limits and usage statistics.
Use Appropriate Commitment Levels
processed
for UI updatesconfirmed
for most operationsfinalized
for critical operationsOptimize Requests
Handle Errors
For technical support or questions about our RPC service:
Interact with Solana nodes using JSON-RPC 2.0
OrbitFlare RPC nodes accept HTTP requests using the JSON-RPC 2.0 specification. This API allows you to interact with the Solana blockchain for querying data and submitting transactions.
To make a JSON-RPC request, send an HTTP POST request with the following specifications:
https://rpc.orbitflare.com
Content-Type: application/json
Field | Type | Description |
---|---|---|
jsonrpc | string | Must be “2.0” |
id | string/number | Unique request identifier |
method | string | The RPC method name |
params | array | Array of method parameters |
Responses will be JSON objects containing:
Field | Type | Description |
---|---|---|
jsonrpc | string | Always “2.0” |
id | string/number | Matches request identifier |
result | varies | The method’s result data |
error | object | Error details (if applicable) |
Many methods accept a commitment
parameter to specify how confirmed the data should be:
processed
: Latest block (fastest, not confirmed)confirmed
: Confirmed by supermajority (balance between speed and finality)finalized
: Finalized by supermajority (slowest, fully confirmed)Example with commitment:
You can send multiple requests in a single HTTP call by providing an array of request objects:
Type | Description |
---|---|
Pubkey | Base-58 encoded public key string |
Hash | Base-58 encoded SHA-256 hash string |
Signature | Base-58 encoded Ed25519 signature |
Slot | Integer block height/slot number |
You can check node health with a GET request:
Possible responses:
ok
: Node is healthy and up-to-datebehind { slots: number }
: Node is behind by N slotserror
: Node is unhealthyRate limits vary by subscription tier. Check your dashboard for your current limits and usage statistics.
Use Appropriate Commitment Levels
processed
for UI updatesconfirmed
for most operationsfinalized
for critical operationsOptimize Requests
Handle Errors
For technical support or questions about our RPC service: