getConfigParam — TON JSON-RPC

Status: Available

Returns one numbered blockchain configuration cell at a masterchain point.

TON RPC node endpoint · Best TON RPC providers compared

POSThttps://triport.io/rpc/ton

Network: TON mainnet
Scope: ton:rpc
Auth: x-token: $TRIPORT_API_KEY
Rate limit: free+; ton_read_rpc_heavy: 15 / 20 / 100 / 250 RPS sustained · short burst 30 / 40 / 200 / 500 (free / basic / pro / business; default, unmeasured); Burst capacity

Endpoint and plans: TON RPC endpoint. Chain check: expected TON value and how to check it.

Request

cURLJavaScriptPython

curl https://triport.io/rpc/ton \
  -H "x-token: $TRIPORT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "getConfigParam",
    "params": { "config_id": 34 }
  }'

const res = await fetch("https://triport.io/rpc/ton", {
  method: "POST",
  headers: {
    "x-token": process.env.TRIPORT_API_KEY,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    "jsonrpc": "2.0",
    "id": 1,
    "method": "getConfigParam",
    "params": {
      "config_id": 34
    }
  }),
});
const data = await res.json();
console.log(data);

import os


import requests


resp = requests.post(
    "https://triport.io/rpc/ton",
    headers={
        "x-token": os.environ["TRIPORT_API_KEY"],
        "Content-Type": "application/json",
    },
    json={
        "jsonrpc": "2.0",
        "id": 1,
        "method": "getConfigParam",
        "params": {
            "config_id": 34,
        },
    },
)
data = resp.json()
print(data)

Response

JSON

Example

{
  "jsonrpc": "2.0",
  "id": 1,
  "result": {
    "config": {
      "bytes": "te6ccgEBAQEAAgAAAA=="
    }
  }
}

Liteserver call over ADNL: liteServer.getConfigParams. See lite_api.tl (checked 2026-10-25).

getConfigParam returns a single numbered TON blockchain configuration cell. The facade maps config_id to a numbered configuration request and returns the serialized cell in the same JSON shape used by getConfigAll.

Use this method when the application already knows the parameter number and does not need the full configuration bag. The captured request asks for configuration parameter 34; the API does not decode the returned cell into validator-set fields.

An optional seqno selects historical masterchain state. Availability follows the chosen liteserver's measured state depth rather than a network-wide archive guarantee.

For a network check, call getConfigParam with params: {"config_id": 19}. Decode the returned cell as a signed 32-bit global ID: TON mainnet is -239 (0xFFFFFF11). This is not an EVM chain ID; see verify the TON network.

Parameters

JSON-RPC params is a by-name object.

Params: object (by-name).

config_idintegerrequired

Signed 32-bit configuration parameter number.

seqnointegeroptional

Non-negative masterchain sequence number; omit for current state.

Response

Response fields

Field	Type	Description
`jsonrpc`	string	JSON-RPC protocol version.
`id`	number or string	Correlates the response with the request.
`result`	object	Configuration-parameter result.
`result.config`	object	Serialized TON configuration cell.
`result.config.bytes`	string	Base64-encoded bag of cells.

The JSON is copied from the accepted live fixture. The fixture sanitizer replaces the cell bytes, so the example documents the wire shape but is not a decodable copy of parameter 34.

Errors

See TON errors for the shared envelope and retention handling.

Code	Meaning	When it happens
`-32602`	Invalid params	`config_id` is absent or not an integer, `seqno` is invalid, or params are positional.
`beyond_retention`	State unavailable	Historical configuration is below the selected server's retained state window.
`-32601`	Method not found	The method is outside the published read-only catalog.
`401`	Unauthorized	The API key is missing or invalid.
`429`	Rate limited	The `ton_read_rpc_heavy` budget is exceeded.

Examples

JavaScript

const response = await fetch("https://triport.io/rpc/ton", {
  method: "POST",
  headers: { "x-token": process.env.TRIPORT_API_KEY, "Content-Type": "application/json" },
  body: JSON.stringify({
    jsonrpc: "2.0", id: "config-34", method: "getConfigParam", params: { config_id: 34 },
  }),
});
const { result } = await response.json();

Notes

config_id and seqno are JSON numbers; the returned BoC is base64 text.
Pruned liteservers had a measured floor of 86 860 000. A genesis-capable node is not proof of continuous history; one measured server had a measured gap.
Named params and batch correlation by id apply to every TON JSON-RPC call.
No REST gateway, write method, or WebSocket configuration subscription is available. Related method: getConfigAll.
TON RPC endpoint and plans.