TriggerSmartContract

post

https://api.shasta.trongrid.io/wallet/triggersmartcontract

Construct an unsigned smart-contract call transaction and return TransactionExtension for client-side signing and broadcast.

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

📘
ABI parameter encoding
The parameter field must be encoded according to the Solidity ABI rules. For examples, see the Solidity ABI specification and Parameter and return value encoding and decoding.

Related resources

GetContractInfo — query contract deployment information, including ABI, bytecode, and Energy settings
TriggerConstantContract — simulate a read-only call without broadcasting a transaction
Sign and broadcast — the API workflow — this API returns an unsigned transaction that must be signed, broadcast, and confirmed
FeeLimit & Energy cost — fee_limit, Energy sharing, and deployer-side contribution
TVM vs. EVM — opcode differences and migration notes

Body Params

owner_address

string

required

Transaction initiator address. (Format: Base58 or Hex)

contract_address

string

required

Contract address. (Format: Base58 or Hex).
Example: TG3XXyExBkPp9nzdajDZsozEu4BkaSJozs

function_selector

string

Function selector.
Example: transfer(address,uint256)

parameter

string

ABI-encoded function arguments only (Hex String); do not include the four-byte function selector. Addresses use the standard 20-byte ABI form without the TRON 41 network prefix.
Example: 00000000000000000000000015208EF33A926919ED270E2FA61367B2DA3753DA0000000000000000000000000000000000000000000000000000000000000032

data

string

This field transmits the necessary data for smart contract interaction, including the function being called and its parameters. You may choose to use the data field, which contains the complete ABI-encoded information, or use the function_selector and parameter fields separately. Note that if both data and function_selector are present, the system will prioritize using the function_selector and parameter fields for the contract interaction.

fee_limit

int64

required

Caller-side Energy budget cap for this contract execution, in sun. It covers both the caller's available Energy, valued at the current Energy price, and the portion that may be paid by burning TRX. It does not include Bandwidth or other transaction fees. Example: 1000000000 (1,000 TRX)

call_value

int64

Defaults to 0

Amount of TRX transferred into the contract. (Unit: sun)

call_token_value

int64

Amount of TRC-10 token transferred into the contract.

token_id

int64

TRC-10 token ID

visible

boolean

Optional. Set to true to format addresses in Base58; set to false for hex format. (Default: false)

Responses

Language

URL

Loading…

Response

Click Try It! to start a request and see the response here! Or choose an example:

application/json

ABI parameter encoding

Related resources

200When the request completes normally, the response body contains the endpoint result. If request processing raises an exception, the HTTP status may still be 200; in that case, the response body contains only the Error field.

400400