SaturnX
  • WELCOME
    • ☀️What is Saturnx?
    • Pricing with Rate limits
      • Prepaid Credits
      • Pay with Crypto
  • RPC Nodes
    • RPCs Overview
  • BLOCKCHAIN
    • Overview
    • HTTP
      • getHistoryCandleStick
      • getHistoryTransaction
      • getAccountTnx
      • getAccountTnxByToken
      • getHoldersTop
      • getHotPairs
      • getTokenSecurity
    • WebSocket
      • {blockchain}.broadcast.transactions
      • {blockchain}.broadcast.kline
    • Kafka
Powered by GitBook
On this page
  • Standard HTTP
  • API Status Codes and Response Format
  1. BLOCKCHAIN

HTTP

Block nodes accept HTTP requests using the JSON-RPC 2.0 specification.

PreviousOverviewNextgetHistoryCandleStick

Last updated 1 month ago

Standard HTTP

Saturnx supports all stable Solana Http.

You can use these with your saturnx URL:

  • Mainnet –

API Status Codes and Response Format

This section outlines the status codes returned by the API and the standard response format used across all endpoints.

Status Codes List

The following table lists the possible status codes returned by the API, along with their meanings:

Code
Status
Description

200

SUCCESS

The operation was completed successfully.

405

VALIDATE_FAILED

The provided API key is unauthorized or invalid.

409

FAILED_INSUFFICIENT

The call failed due to insufficient balance or resources.

500

FAILED

An internal server error occurred, preventing the operation from completing.

Response Format

All API responses adhere to the following JSON structure:

{
    "code": 200,
    "message": "Operation Successful",
    "data": {}
}

code: An integer representing the status of the request (see the status codes list above).

message: A human-readable string describing the result of the operation (e.g., success or error details).

data: An object containing the response data. This field will be populated with relevant data when the request is successful (e.g., a list of transactions for SUCCESS), or it will be null or an empty object {}

https://api.saturnx.dev