getVersion — Solana JSON-RPC

Status: Available

Returns the version of the Solana software running on the node serving your request.

POSThttps://triport.io/sol

Network: Solana
Auth: x-token: $TRIPORT_API_KEY (or Authorization: Bearer)
Rate limit: free+ — 20 rps (free) · 60 rps (basic) · 200 rps (pro) · 600 rps (business)

Endpoint and plans: Solana RPC endpoint.

Request

cURLJavaScriptPython

curl https://triport.io/sol \
  -H "Authorization: Bearer $TRIPORT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "getVersion",
    "params": []
  }'

const res = await fetch("https://triport.io/sol", {
  method: "POST",
  headers: {
    "Authorization": `Bearer ${process.env.TRIPORT_API_KEY}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    "jsonrpc": "2.0",
    "id": 1,
    "method": "getVersion",
    "params": []
  }),
});
const data = await res.json();
console.log(data);

import os


import requests


resp = requests.post(
    "https://triport.io/sol",
    headers={
        "Authorization": f"Bearer {os.environ['TRIPORT_API_KEY']}",
        "Content-Type": "application/json",
    },
    json={
        "jsonrpc": "2.0",
        "id": 1,
        "method": "getVersion",
        "params": [],
    },
)
data = resp.json()
print(data)

Response

JSON

Example

{
  "jsonrpc": "2.0",
  "id": 1,
  "result": {
    "solana-core": "1.18.22",
    "feature-set": 3469865029
  }
}

getVersion reports the Solana software running on the node that handled your request. It takes no parameters and returns a small object with two fields: the human-readable solana-core release string and the numeric feature-set identifier that the node currently advertises.

Use it to confirm which cluster build is behind your endpoint — for example, to verify that a feature you depend on has shipped, or to log the node version alongside diagnostics when a response looks unexpected. Because it is cheap and parameter-free, it also doubles as a lightweight check that your endpoint and API key are wired up correctly.

The feature-set integer is a hash of the set of runtime features active on the node. Two nodes on the same release line can report the same solana-core string while differing on feature-set during a feature-activation rollout, so treat feature-set — not the version string — as the authoritative signal when you need to know exactly which features are live.

Parameters

This method takes no parameters. Send an empty params array.

——optional

No parameters. params must be [].

Response

Response fields

Field	Type	Description
`result`	object	The `Version` object.
`result.solana-core`	string	The Solana core release running on the node (e.g. `1.18.22`).
`result.feature-set`	integer (`u32`)	Identifier of the runtime feature set the node currently advertises.

Errors

getVersion uses the standard JSON-RPC error envelope. See errors for the full structure.

Code	Meaning	When it happens
`401`	Unauthorized	Missing or invalid `Authorization: Bearer` token.
`429`	Rate limited	You exceeded your tier's RPS for `sol_read_rpc`.

Examples

JavaScript (fetch)

JavaScript

const res = await fetch("https://triport.io/sol", {
  method: "POST",
  headers: {
    "Authorization": `Bearer ${process.env.TRIPORT_API_KEY}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    jsonrpc: "2.0",
    id: 1,
    method: "getVersion",
    params: [],
  }),
});


const { result } = await res.json();
console.log("solana-core:", result["solana-core"]); // 1.18.22
console.log("feature-set:", result["feature-set"]); // 3469865029

Notes

Parameter-free. getVersion carries no params and returns a small fixed object, so — like getSlot and getHealth — it is a convenient connectivity and key-validity probe.
feature-set vs solana-core. The version string tracks the release; the feature-set integer tracks which runtime features are active. Use feature-set when you must know exactly which features a node has enabled.
Per-node value. The version reflects the specific backend that served your request; behind a load-balanced endpoint, successive calls can be served by nodes on slightly different builds during a cluster upgrade.
Related methods: getHealth, getIdentity, and getGenesisHash for other node/cluster-identity reads.