getchainparameters — Tron Wallet API

Returns the current native Tron chain-parameter object.

POSThttps://triport.io/rpc/tron/wallet/getchainparameters

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

Request

cURLJavaScriptPython

curl https://triport.io/rpc/tron/wallet/getchainparameters \
  -H "x-token: $TRIPORT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{}'

const res = await fetch("https://triport.io/rpc/tron/wallet/getchainparameters", {
  method: "POST",
  headers: {
    "x-token": process.env.TRIPORT_API_KEY,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({}),
});
const data = await res.json();
console.log(data);

import os


import requests


resp = requests.post(
    "https://triport.io/rpc/tron/wallet/getchainparameters",
    headers={
        "x-token": os.environ["TRIPORT_API_KEY"],
        "Content-Type": "application/json",
    },
    json={},
)
data = resp.json()
print(data)

Response

JSON

Example

{}

getchainparameters returns the native network parameters visible at the time the request is served. It is intended for clients that need the wallet-layer chain configuration rather than one EVM-compatible scalar.

The response is a current snapshot. The request does not accept a block number, so it cannot be used to reconstruct historical chain-parameter state.

Parameters

The request body is a required empty JSON object.

bodyobjectrequired

Must be {}; additional properties are rejected by the contract.

Response

tron.yaml defines an extensible wallet object without a response example, so {} is a schema-valid placeholder. The dated parameters below describe an observed subset rather than a closed response contract.

responseobject

Current chain parameters; field names are not enumerated by the contract.

Errors

Wallet failures use HTTP status plus JSON. See Tron errors.

HTTP	Meaning	When it happens
`400`	Bad request	The request body is malformed or contains fields.
`401`	Unauthorized	The API key is missing or invalid.
`403`	Forbidden	The scope or tier does not permit the request.
`429`	Rate limited	The `tron_read_rpc` budget is exceeded.

Examples

JavaScript

const response = await fetch("https://triport.io/rpc/tron/wallet/getchainparameters", {
  method: "POST",
  headers: { "x-token": process.env.TRIPORT_API_KEY, "Content-Type": "application/json" },
  body: "{}",
});
const parameters = await response.json();

Notes

This is current chain state; no historical selector exists in the schema.
Consumers should tolerate contract-permitted additional response properties.
Related: getnextmaintenancetime.