TRON

The TRON Gateway provides both JSON-RPC and the native TRON HTTP API. Its native asset is TRX, and it is the only currently exposed chain with two transports.

Supported networks

Copy complete Access Points from the dashboard instead of constructing domains from the Hosts.

Endpoint-free JSON-RPC

On an Accelerator hit, TRON JSON-RPC eth_blockNumber can return a result without an Endpoint. Other TRON JSON-RPC methods, parameter variants, and writes require an Endpoint. See Accelerator for the complete boundary.

Configure complete JSON-RPC access

Provider sync does not currently cover TRON. Manually add a JSON-RPC Endpoint on the same network, add it to the default JSON-RPC route, then verify it with eth_chainId, which is not an Accelerator method:

curl '<tron_jsonrpc_access_point>' \
  -H 'Authorization: Bearer <app_api_key>' \
  -H 'Content-Type: application/json' \
  --data '{"jsonrpc":"2.0","id":1,"method":"eth_chainId","params":[]}'

HTTP API setup

The dashboard cannot currently complete HTTP API route setup. Before use, ask a platform administrator to add an http_api Endpoint to the target Gateway HTTP API route.

Accelerator does not apply to the HTTP API; this path always requires an Endpoint.

curl -X POST '<tron_httpapi_access_point>/wallet/getnowblock' \
  -H 'Authorization: Bearer <app_api_key>' \
  -H 'Content-Type: application/json' \
  --data '{}'

Current limits

• JSON-RPC supports single HTTP calls only; batch, WebSocket, and public gRPC are not supported.
• The HTTP API accepts GET and POST only and exposes /wallet/*, /walletsolidity/*, and /v1/* only.
• /walletpbft/* and other path families are not supported.
• Method and historical data availability depends on upstream Endpoints. Mainnet and Nile never fail over across networks.

See TRON HTTP API for forwarding, response, and retry behavior.