For the complete documentation index, see llms.txt. This page is also available as Markdown.

Tron gRPC API

gRPC API reference for TRON blockchain. Explore service list, request examples, and how to connect to GetBlock's TRON RPC endpoints

TRON nodes expose the same operation set as the REST API over gRPC, using Protocol Buffers. gRPC is the transport used internally by java-tron and by performance-sensitive backends; the request and response messages mirror the REST endpoints one-to-one.

The GetBlock TRON reference documents the REST (HTTP) and JSON-RPC interfaces in full. This page describes the gRPC transport and how its services map to the documented REST endpoints, so a gRPC integration can reuse the same request and response shapes.

Services

TRON's protobuf API is organized into two services that correspond to the two node types:

Service
Node
Corresponds to

Wallet

Fullnode

The /wallet/{method} REST endpoints (full API)

WalletSolidity

Solidity

The /walletsolidity/{method} REST endpoints (confirmed reads)

Method mapping

Each gRPC method maps to a REST endpoint of the same name; the protobuf request and response messages carry the same fields documented on the REST pages.

gRPC method (Wallet service)
REST endpoint
Reference

GetAccount

/wallet/getaccount

GetNowBlock

/wallet/getnowblock

GetBlockByNum

/wallet/getblockbynum

GetTransactionById

/wallet/gettransactionbyid

TriggerConstantContract

/wallet/triggerconstantcontract

TriggerContract

/wallet/triggersmartcontract

BroadcastTransaction

/wallet/broadcasttransaction

FreezeBalanceV2

/wallet/freezebalancev2

The protobuf service and message definitions are maintained in the java-tron repository (api/api.proto, core/*.proto). Use those definitions to generate a gRPC client, then send requests to the GetBlock TRON endpoint.

Reading the field shapes

Because the gRPC messages and the REST JSON bodies carry the same fields, the parameter and response tables on the REST pages are also the reference for gRPC request and response fields. For request and response detail, see the corresponding endpoint under the REST API.

Support

For technical support and questions:

See Also

Last updated

Was this helpful?