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, e.g. Ethereum, Bitcoin, etc.
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 network like "nile" is a test network.
Defines the specific source address for the transaction.
Defines the unique ID of the Wallet.
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.
Represents the Secret Key value provided by the customer. This field is used for security purposes during the callback notification, in order to prove the sender of the callback as Crypto APIs. For more information please see our Documentation.
Represents the URL that is set by the customer where the callback will be received at. The callback notification will be received only if and when the event occurs. We support ONLY httpS type of protocol
.
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.
Token identifier - for BITCOIN BASED should be property id e.g 31 for ETHEREUM BASED shoud be contract e.g 0xdac17f958d2ee523a2206206994597c13d831ec7
Specifies the version of the API that incorporates this endpoint.
Defines the ID of the request. The requestId
is generated by Crypto APIs 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 the Secret Key value provided by the customer. This field is used for security purposes during the callback notification, in order to prove the sender of the callback as Crypto APIs. For more information please see our Documentation.
Represents the URL that is set by the customer where the callback will be received at. The callback notification will be received only if and when the event occurs. We support ONLY httpS type of protocol
.
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 which depends on its type - if it is a Coin or Token.
Defines the contract address in the blockchain for an ERC20 token.
Defines the fee limit value.
Defines the Token symbol.
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.
Specifies the version of the API that incorporates this endpoint.
Represents a unique identifier that serves as reference to the specific request which prompts a callback, e.g. Blockchain Events Subscription, Blockchain Automation, etc.
Specifies a unique ID generated by the system and attached to each callback. It is used by the server to recognize consecutive requests with the same data with the purpose not to perform the same operation twice.
Specifies all data, as attributes, included into the callback notification, which depends on the event
.
Represents the Crypto APIs 2.0 product which sends the callback.
Defines the specific event, for which a callback subscription is set.
Defines an item
as one result.
Represents the specific blockchain protocol name, e.g. Ethereum, Bitcoin, etc.
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", "sepolia", "mordor" are test networks.
The required number of approvals needed to approve the transaction.
The required number of rejections needed to reject the transaction.
The current number of approvals given for the transaction.
The current number of rejections given for the transaction.
API Key
{
"context": "yourExampleString",
"data": {
"item": {
"amount": "0.25684",
"callbackSecretKey": "yourSecretString",
"callbackUrl": "https://example.com",
"feeLimit": "1000000000",
"note": "yourAdditionalInformationhere",
"recipientAddress": "TMVeigwYyuXJVHER4oA2yQzsFFSN2JfXkt",
"tokenIdentifier": "TF17BgPaZYbz8oxbjhriubPDsA7ArKoLX3"
}
}
}
{
"apiVersion": "2023-04-25",
"requestId": "601c1710034ed6d407996b30",
"context": "yourExampleString",
"data": {
"item": {
"callbackSecretKey": "yourSecretString",
"callbackUrl": "https://example.com",
"note": "yourAdditionalInformationhere",
"recipient": [
{
"address": "TMVeigwYyuXJVHER4oA2yQzsFFSN2JfXkt",
"amount": "0.2568",
"unit": "JST"
}
],
"sender": {
"address": "TX8VXpdEoNNrKeEuNTfbEXfa9eZivcyUwD"
},
"tokenTypeSpecificData": {
"contractAddress": "TF17BgPaZYbz8oxbjhriubPDsA7ArKoLX3",
"feeLimit": "1000000000",
"symbol": "JST"
},
"transactionRequestId": "62daacdbc8a7282e9ea01c35"
}
}
}
{
"apiVersion": "2021-03-20",
"referenceId": "6038d09050653d1f0e40584c",
"idempotencyKey": "e55bf7a4a7188855f1c27541a6c387d04cc3b22ee34d1304b0e6ecad61c9906c",
"data": {
"product": "WALLET_AS_A_SERVICE",
"event": "TRANSACTION_REQUEST_APPROVAL",
"item": {
"blockchain": "Bitcoin/Ethereum (whichever applicable)",
"network": "Testnet/Mainnet (whichever applicable)",
"requiredApprovals": 2,
"requiredRejections": 2,
"currentApprovals": 1,
"currentRejections": 0
}
}
}