Through this endpoint customers can make a single feeless token transaction on the Tron blockchain protocol. TRX transactions burn certain resources called Bandwidth and Energy. Each account has 1500 bandwidth free for use every 24 hours and more can be obtained by staking TRX. The unit price of Energy is 280 SUN and of bandwidth - 1000 SUN. If the resources are insufficient, TRX will be burned to pay for them.
Represents the specific blockchain protocol name.
Represents the name of the blockchain network used; blockchain networks are usually identical as technology and software, but they differ in data, e.g. - "mainnet" is the live network with actual data while networks like "testnet", "nile" are test networks.
Defines the specific source address for the transaction.
Defines the unique ID of the Vault.
In batch situations the user can use the context to correlate responses with requests. This property is present regardless of whether the response was successful or returned as an error. context
is specified by the user.
In batch situations the user can use the context to correlate responses with requests. This property is present regardless of whether the response was successful or returned as an error. context
is specified by the user.
Represents the specific amount of the transaction.
Fee limit of the smart contract. If "OUT_OF_ENERGY" error appears - It is necessary to check whether the address of the calling contract has TRX and whether it is enough to pay for the burning energy or bandwidth cost, otherwise the address needs to obtain enough TRX. If there is enough TRX, the feeLimit set by the transaction is smaller, and it needs to be increased.
Represents an optional note to add a free text in, explaining or providing additional detail on the transaction request.
Defines the specific recipient address for the transaction.
The specific contract address.
Specifies the version of the API that incorporates this endpoint.
Defines the ID of the request. The requestId
is generated by Vaultody and it's unique for every request.
In batch situations the user can use the context to correlate responses with requests. This property is present regardless of whether the response was successful or returned as an error. context
is specified by the user.
Represents an optional note to add a free text in, explaining or providing additional detail on the transaction request.
Defines the destination for the transaction, i.e. the recipient(s).
Defines the destination address.
Defines the amount sent to the destination address.
Represents the unit of the tokens amount recieved.
Defines details about the source, i.e. the sender.
Defines the sender's public address.
Represents the specific token data.
Defines the contract address in the blockchain for an TRC-20 token.
Defines the fee limit value.
Defines the Token symbol, e.g JST, USDT.
Represents a unique identifier of the transaction request (the request sent to make a transaction), which helps in identifying which callback and which referenceId
concern that specific transaction request.
cb233681a8ee35665296c1824c1f67bc46691788
PSqeqRLap8rBc/wogNU1DeGGUPb2VyVtg6GiBOaBnYQ=
1681885776
zYgKeueoOq
{
"context": "yourExampleString",
"data": {
"item": {
"amount": "0.25684",
"feeLimit": "1000000000",
"note": "yourAdditionalInformationhere",
"recipientAddress": "TMVeigwYyuXJVHER4oA2yQzsFFSN2JfXkt",
"tokenIdentifier": "TF17BgPaZYbz8oxbjhriubPDsA7ArKoLX3"
}
}
}
{
"apiVersion": "2024-05-09",
"requestId": "601c1710034ed6d407996b30",
"context": "yourExampleString",
"data": {
"item": {
"note": "yourAdditionalInformationhere",
"recipient": [
{
"address": "TMVeigwYyuXJVHER4oA2yQzsFFSN2JfXkt",
"amount": "0.2568",
"unit": "JST"
}
],
"sender": {
"address": "TX8VXpdEoNNrKeEuNTfbEXfa9eZivcyUwD"
},
"tokenTypeSpecificData": {
"contractAddress": "TF17BgPaZYbz8oxbjhriubPDsA7ArKoLX3",
"feeLimit": "1000000000",
"symbol": "JST"
},
"transactionRequestId": "62daacdbc8a7282e9ea01c35"
}
}
}