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.

Supports Callback Functionality Single Result - This endpoint returns only one single result. POST /wallet-as-a-service/wallets/{walletId}/{blockchain}/{network}/addresses/{senderAddress}/feeless-token-transaction-requests

Path Parameters

  • Required
    blockchain string

    Represents the specific blockchain protocol name, e.g. Ethereum, Bitcoin, etc.

    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", "ropsten" are test networks.

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

    Defines the specific source address for the transaction.

    Example : TX8VXpdEoNNrKeEuNTfbEXfa9eZivcyUwD
  • Required
    walletId string

    Defines the unique ID of the Wallet.

    Example : 62b9b5c3b97f4b0008092714

Query parameters

  • 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
        callbackSecretKey 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
      • Optional
        callbackUrl 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
      • Required
        feeLimit string

        Fee limit of the smart contract

        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

        Token identifier - for BITCOIN BASED should be property id e.g 31 for ETHEREUM BASED shoud be contract e.g 0xdac17f958d2ee523a2206206994597c13d831ec7

        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 : 2021-03-20
  • Required
    requestId string

    Defines the ID of the request. The requestId is generated by Crypto APIs 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
        callbackSecretKey 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
      • Optional
        callbackUrl 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
      • 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).

        • 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.

        • Required
          address string

          Defines the sender's public address.

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

          Defines the contract address in the blockchain for an ERC20 token.

          Example : TF17BgPaZYbz8oxbjhriubPDsA7ArKoLX3
        • Required
          feeLimit string

          Defines the fee limit value.

          Example : 1000000000
        • Required
          symbol string

          Defines the Token symbol.

          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

Callback parameters Method : POST

You can use the optional parameter callbackSecretKey in your request for additional security. It is then used to create a unique hash string in the x-signature response header in the callback request itself. For more information, please see our Documentation.
TRANSACTION_REQUEST_APPROVAL TRANSACTION_REQUEST_REJECTION TRANSACTION_REQUEST_BROADCASTED TRANSACTION_REQUEST_MINED TRANSACTION_REQUEST_FAIL

Content-Type : application/json

  • Object :

  • Required
    apiVersion string

    Specifies the version of the API that incorporates this endpoint.

    Example : 2021-03-20
  • Required
    referenceId 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
  • Required
    idempotencyKey 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
  • Required
    data object

    Specifies all data, as attributes, included into the callback notification, which depends on the event.

    • Required
      product string

      Represents the Crypto APIs 2.0 product which sends the callback.

      Example : WALLET_AS_A_SERVICE
    • Required
      event string

      Defines the specific event, for which a callback subscription is set.

      Example : TRANSACTION_REQUEST_APPROVAL
    • Required
      item object

      Defines an item as one result.

      • Required
        blockchain string

        Represents the specific blockchain protocol name, e.g. Ethereum, Bitcoin, etc.

        Example : ethereum
      • 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", "ropsten", "rinkeby" are test networks.

        Example : ropsten
      • Required
        requiredApprovals integer

        The required number of approvals needed to approve the transaction.

        Example : 2
      • Required
        requiredRejections integer

        The required number of rejections needed to reject the transaction.

        Example : 2
      • Required
        currentApprovals integer

        The current number of approvals given for the transaction.

        Example : 1
      • Required
        currentRejections integer

        The current number of rejections given for the transaction.

        Example : 0

Credits Cost : 500 Credits For 1 Result(s)

Try it out

Request Example

POST
https://rest.cryptoapis.io/wallet-as-a-service/wallets/62b9b5c3b97f4b0008092714/tron/nile/addresses/TX8VXpdEoNNrKeEuNTfbEXfa9eZivcyUwD/feeless-token-transaction-requests?context=yourExampleString
Headers
Content-Type: application/json
X-API-Key: my-api-key

Request Body
{
    "context": "yourExampleString",
    "data": {
        "item": {
            "amount": "0.25684",
            "callbackSecretKey": "yourSecretString",
            "callbackUrl": "https://example.com",
            "feeLimit": "1000000000",
            "note": "yourAdditionalInformationhere",
            "recipientAddress": "TMVeigwYyuXJVHER4oA2yQzsFFSN2JfXkt",
            "tokenIdentifier": "TF17BgPaZYbz8oxbjhriubPDsA7ArKoLX3"
        }
    }
}

Response Example

{
    "apiVersion": "2021-03-20",
    "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"
        }
    }
}

Callback Example

{
    "apiVersion": "2021-03-20",
    "referenceId": "6038d09050653d1f0e40584c",
    "idempotencyKey": "e55bf7a4a7188855f1c27541a6c387d04cc3b22ee34d1304b0e6ecad61c9906c",
    "data": {
        "product": "WALLET_AS_A_SERVICE",
        "event": "TRANSACTION_REQUEST_APPROVAL",
        "item": {
            "blockchain": "ethereum",
            "network": "ropsten",
            "requiredApprovals": 2,
            "requiredRejections": 2,
            "currentApprovals": 1,
            "currentRejections": 0
        }
    }
}