TriportRPC

getVersion

POSThttps://api.triport.io/

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

Solanafree+ — 20 rps (free) · 60 rps (basic) · 200 rps (pro) · 600 rps (business)

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

FieldTypeDescription
resultobjectThe Version object.
result.solana-corestringThe Solana core release running on the node (e.g. 1.18.22).
result.feature-setinteger (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.

CodeMeaningWhen it happens
401UnauthorizedMissing or invalid Authorization: Bearer token.
429Rate limitedYou exceeded your tier's RPS for sol_read_rpc.

Examples

JavaScript (fetch)

const res = await fetch("https://api.triport.io/", {
  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

TypeScript SDK (@triport/sdk)

import { TriportClient } from "@triport/sdk";


const client = new TriportClient({ apiKey: process.env.TRIPORT_API_KEY! });


const version = await client.solana.getVersion();
console.log("solana-core:", version["solana-core"]);
console.log("feature-set:", version["feature-set"]);

Python (triport-sdk)

import os
from triport import TriportClient


client = TriportClient(api_key=os.environ["TRIPORT_API_KEY"])


version = client.solana.get_version()
print("solana-core:", version["solana-core"])
print("feature-set:", version["feature-set"])

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.