GuidesAPI ReferenceCommunityDiscordBlogFAQBug BountyAnnouncements
API Reference
Chinese(中文版)
  1. FullNode HTTP API
  2. Smart Contracts

TriggerConstantContract

post
https://api.shasta.trongrid.io/wallet/triggerconstantcontract

Invoke the readonly function (modified by the view or pure modifier) of a contract for contract data query; or Invoke the non-readonly function of a contract for predicting whether the transaction can be successfully executed and estimating the energy consumption; or estimate the energy consumption of contract deployment

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…

Note:

  • TriggerConstantContract operation will not generate an on-chain transaction, nor will it change the status of the current node.

Related resources

  • Triggersmartcontract 1 1 — previous in this section
  • Wallet Deploycontract — next in this section
  • This endpoint does not require a transaction-level fee_limit and does not consume the account's actual Bandwidth or Energy. Simulation is still subject to node configuration and protective TVM execution limits.
  • FeeLimit — use the returned energy_used to size the real transaction's Energy budget
  • TVM — execution semantics and node-side execution limits
Body Params
string
required

Transaction initiator address. (Format: Base58 or Hex)

string

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

string

Function selector.
Example: transfer(address,uint256)

string

ABI-encoded function parameters (Hex String).
Example: 000000000000000000000000a614f803b6fd780986a42c78ec9c7f77e6ded13c

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.

int64

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

int64

Amount of TRC-10 token transferred into the contract.

int64

TRC-10 token id

boolean
Defaults to true

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

Responses

Updated 7 days ago

Language
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json

Updated 7 days ago