Skip to main content

Overview

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.

Request Format

To make a JSON-RPC request, send an HTTP POST request with the following specifications:
  • Endpoint: https://fra.rpc.orbitflare.com?api_key=YOUR_LICENSE_KEY
  • Header: Content-Type: application/json
  • Body: JSON object with these fields:

Example Request

Response Format

Responses will be JSON objects containing:

Commitment

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:

Batch Requests

You can send multiple requests in a single HTTP call by providing an array of request objects:

Common Types

Health Check

You can check node health with a GET request:
Possible responses:
  • ok: Node is healthy and up-to-date
  • behind { slots: number }: Node is behind by N slots
  • error: Node is unhealthy

Available Methods

Account & Program

  • getAccountInfo
  • getMultipleAccounts
  • getProgramAccounts
  • getMinimumBalanceForRentExemption

Blocks & Slots

  • getBlock
  • getBlocks
  • getBlockHeight
  • getSlot
  • getSlotLeader

Transactions

  • getTransaction
  • getSignatureStatuses
  • getSignaturesForAddress
  • sendTransaction
  • simulateTransaction

Tokens

  • getTokenAccountBalance
  • getTokenAccountsByDelegate
  • getTokenAccountsByOwner
  • getTokenSupply

Rate Limits

Rate limits vary by subscription tier. See the Authentication & Limits page for the exact RPS and TPS values per plan.

Best Practices

  1. Use Appropriate Commitment Levels
    • Use processed for UI updates
    • Use confirmed for most operations
    • Use finalized for critical operations
  2. Optimize Requests
    • Use batch requests when possible
    • Implement proper caching
    • Choose appropriate polling intervals
  3. Handle Errors
    • Implement proper error handling
    • Use exponential backoff for retries
    • Monitor request failures

See Also

Authentication & Limits

API key setup, endpoint formats, rate limits, and connection limits.

Error Codes

HTTP status codes, JSON-RPC errors, and how to handle them.

WebSocket API

Real-time subscriptions for accounts, slots, logs, and more.

Support

For technical support or questions about our RPC service: