getVersion
https://api.triport.io/Returns the version of the Solana software running on the node serving your request.
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.
——optionalparams 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)
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"]); // 3469865029TypeScript 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.
getVersioncarries no params and returns a small fixed object, so — likegetSlotandgetHealth— it is a convenient connectivity and key-validity probe. feature-setvssolana-core. The version string tracks the release; thefeature-setinteger tracks which runtime features are active. Usefeature-setwhen 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, andgetGenesisHashfor other node/cluster-identity reads.