Create Fungible Token Transaction Request From Address Without Fee Priority
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.
Path Parameters
-
Requiredblockchain string
Represents the specific blockchain protocol name, e.g. Ethereum, Bitcoin, etc.
-
Requirednetwork string
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", "ropsten" are test networks.
-
RequiredsenderAddress string
Defines the specific source address for the transaction.
-
RequiredwalletId string
Defines the unique ID of the Wallet.
Query parameters
-
Optionalcontext string
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.
Request body schema application/json
-
Optionalcontext string
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. -
Requireddata object
-
Requireditem object
-
Requiredamount string
Represents the specific amount of the transaction.
-
OptionalcallbackSecretKey string
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.
-
OptionalcallbackUrl string
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
. -
OptionalfeeLimit string
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.
-
Optionalnote string
Represents an optional note to add a free text in, explaining or providing additional detail on the transaction request.
-
RequiredrecipientAddress string
Defines the specific recipient address for the transaction.
-
RequiredtokenIdentifier string
Token identifier - for BITCOIN BASED should be property id e.g 31 for ETHEREUM BASED shoud be contract e.g 0xdac17f958d2ee523a2206206994597c13d831ec7
-
-
Response schema
Content-Type: application/json
The resource has been successfully created.
Object :
-
RequiredapiVersion string
Specifies the version of the API that incorporates this endpoint.
Example : 2021-03-20 -
RequiredrequestId string
Defines the ID of the request. The
requestId
is generated by Crypto APIs and it's unique for every request.Example : 601c1710034ed6d407996b30 -
Optionalcontext string
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.Example : yourExampleString -
Requireddata object
-
Requireditem object
-
OptionalcallbackSecretKey string
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.
Example : yourSecretString -
OptionalcallbackUrl string
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
.Example : https://example.com -
Optionalnote string
Represents an optional note to add a free text in, explaining or providing additional detail on the transaction request.
Example : yourAdditionalInformationhere -
Requiredrecipient array
Defines the destination for the transaction, i.e. the recipient(s).
-
Requiredaddress string
Defines the destination address.
Example : TMVeigwYyuXJVHER4oA2yQzsFFSN2JfXkt -
Requiredamount string
Defines the amount sent to the destination address.
Example : 0.2568 -
Requiredunit string
Represents the unit of the tokens amount recieved.
Example : JST
-
-
Requiredsender object
Defines details about the source, i.e. the sender.
-
Requiredaddress string
Defines the sender's public address.
Example : TX8VXpdEoNNrKeEuNTfbEXfa9eZivcyUwD
-
-
RequiredtokenTypeSpecificData object One Ofobject
-
RequiredcontractAddress string
Defines the contract address in the blockchain for an ERC20 token.
Example : TF17BgPaZYbz8oxbjhriubPDsA7ArKoLX3 -
RequiredfeeLimit string
Defines the fee limit value.
Example : 1000000000 -
Requiredsymbol string
Defines the Token symbol.
Example : JST
-
-
RequiredtransactionRequestId string
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.Example : 62daacdbc8a7282e9ea01c35
-
-
Callback parameters Method : POST
Content-Type : application/json
Object :
-
RequiredapiVersion string
Specifies the version of the API that incorporates this endpoint.
Example : 2021-03-20 -
RequiredreferenceId string
Represents a unique identifier that serves as reference to the specific request which prompts a callback, e.g. Blockchain Events Subscription, Blockchain Automation, etc.
Example : 6038d09050653d1f0e40584c -
RequiredidempotencyKey string
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.
Example : e55bf7a4a7188855f1c27541a6c387d04cc3b22ee34d1304b0e6ecad61c9906c -
Requireddata object
Specifies all data, as attributes, included into the callback notification, which depends on the
event
.-
Requiredproduct string
Represents the Crypto APIs 2.0 product which sends the callback.
Example : WALLET_AS_A_SERVICE -
Requiredevent string
Defines the specific event, for which a callback subscription is set.
Example : TRANSACTION_REQUEST_APPROVAL -
Requireditem object
Defines an
item
as one result.-
Requiredblockchain string
Represents the specific blockchain protocol name, e.g. Ethereum, Bitcoin, etc.
Example : ethereum -
Requirednetwork string
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", "ropsten", "rinkeby" are test networks.
Example : ropsten -
RequiredrequiredApprovals integer
The required number of approvals needed to approve the transaction.
Example : 2 -
RequiredrequiredRejections integer
The required number of rejections needed to reject the transaction.
Example : 2 -
RequiredcurrentApprovals integer
The current number of approvals given for the transaction.
Example : 1 -
RequiredcurrentRejections integer
The current number of rejections given for the transaction.
Example : 0
-
-