Additionally, paste this code immediately after the opening tag:

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.

key.singleItemTitle POST /vaults/{vaultId}/{blockchain}/{network}/addresses/{senderAddress}/feeless-token-transaction-requests

Path Parameters

  • Required
    blockchain string

    Represents the specific blockchain protocol name.

    Example : tron
    Possible Values : tron
  • Required
    network 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", "nile" are test networks.

    Example : nile
    Possible Values : mainnet nile
  • Required
    senderAddress string

    Defines the specific source address for the transaction.

    Example : TX8VXpdEoNNrKeEuNTfbEXfa9eZivcyUwD
  • Required
    vaultId string

    Defines the unique ID of the Vault.

    Example : 62b9b5c3b97f4b0008092714

Query Paramaters

  • Optional
    context 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

Request Body Schema application/json

  • Optional
    context 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
  • Required
    data object
    • Required
      item object
      • Required
        amount string

        Represents the specific amount of the transaction.

        Example : 0.25684
      • Optional
        feeLimit 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.

        Example : 1000000000
      • Optional
        note string

        Represents an optional note to add a free text in, explaining or providing additional detail on the transaction request.

        Example : yourAdditionalInformationhere
      • Required
        recipientAddress string

        Defines the specific recipient address for the transaction.

        Example : TMVeigwYyuXJVHER4oA2yQzsFFSN2JfXkt
      • Required
        tokenIdentifier string

        The specific contract address.

        Example : TF17BgPaZYbz8oxbjhriubPDsA7ArKoLX3

Response Schema

201 400 401 402 403 409 415 422 429 500
Http Status Code: 201
Content Type: application/json

The resource has been successfully created.

  • Object :

  • Required
    apiVersion string

    Specifies the version of the API that incorporates this endpoint.

    Example : 2024-05-09
  • Required
    requestId string

    Defines the ID of the request. The requestId is generated by Vaultody and it's unique for every request.

    Example : 601c1710034ed6d407996b30
  • Optional
    context 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
  • Required
    data object
    • Required
      item object
      • Optional
        note string

        Represents an optional note to add a free text in, explaining or providing additional detail on the transaction request.

        Example : yourAdditionalInformationhere
      • Required
        recipient array

        Defines the destination for the transaction, i.e. the recipient(s).

        Example : TUwJLr6f3oorDdoGTwyPGo2JAu6aiPVtYw
        • Required
          address string

          Defines the destination address.

          Example : TMVeigwYyuXJVHER4oA2yQzsFFSN2JfXkt
        • Required
          amount string

          Defines the amount sent to the destination address.

          Example : 0.2568
        • Required
          unit string

          Represents the unit of the tokens amount recieved.

          Example : JST
      • Required
        sender object

        Defines details about the source, i.e. the sender.

        Example : TX8VXpdEoNNrKeEuNTfbEXfa9eZivcyUwD
        • Required
          address string

          Defines the sender's public address.

          Example : TX8VXpdEoNNrKeEuNTfbEXfa9eZivcyUwD
      • Required
        tokenTypeSpecificData object object One Of
        object
        • Required
          contractAddress string

          Defines the contract address in the blockchain for an TRC-20 token.

          Example : TF17BgPaZYbz8oxbjhriubPDsA7ArKoLX3
        • Required
          feeLimit string

          Defines the fee limit value.

          Example : 1000000000
        • Required
          symbol string

          Defines the Token symbol, e.g JST, USDT.

          Example : JST
      • Required
        transactionRequestId 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

Request Example

POST
https://rest.vaultody.com/vaults/62b9b5c3b97f4b0008092714/tron/nile/addresses/TX8VXpdEoNNrKeEuNTfbEXfa9eZivcyUwD/feeless-token-transaction-requests?context=yourExampleString
Headers
Content-Type: application/json
x-api-key: cb233681a8ee35665296c1824c1f67bc46691788
x-api-sign: PSqeqRLap8rBc/wogNU1DeGGUPb2VyVtg6GiBOaBnYQ=
x-api-timestamp: 1681885776
x-api-passphrase: zYgKeueoOq

Request Body
{
    "context": "yourExampleString",
    "data": {
        "item": {
            "amount": "0.25684",
            "feeLimit": "1000000000",
            "note": "yourAdditionalInformationhere",
            "recipientAddress": "TMVeigwYyuXJVHER4oA2yQzsFFSN2JfXkt",
            "tokenIdentifier": "TF17BgPaZYbz8oxbjhriubPDsA7ArKoLX3"
        }
    }
}

Response Example

{
    "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"
        }
    }
}