Create Coins Transaction Request from Address

Through this endpoint users can create a new single transaction request from one address to another.

POST /wallet-as-a-service/wallets/{walletId}/{blockchain}/{network}/addresses/{address}/transaction-requests

Path Parameters

  • Required
    address string

    Defines the specific source address for the transaction.

    Example : 0x6f61e3c2fbb8c8be698bd0907ba6c04b62800fe5
  • Required
    blockchain string

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

    Example : ethereum
    Possible Values : 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.

    Possible Values : mainnet
  • Required
    walletId string

    Represents the sender's specific and unique Wallet ID of the sender.

    Example : 609e221675d04500068718dc

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.

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.

  • Required
    data object
    • Required
      item object
      • Required
        amount string

        Represents the specific amount of the transaction.

        Example : 0.2
      • Required
        feePriority string

        Represents the fee priority of the automation, whether it is "slow", "standard" or "fast".

        Example : slow
        Possible Values : slow standard fast
      • Required
        toAddress string

        Defines the specific recipient address for the transaction.

        Example : 0xc065b539490f81b6c297c37b1925c3be2f190732

Response schema

200 400 401 402 403 409 415 422 429 500
HTTP Status Code: 200
Content-Type: application/json

The request has been successful.

  • Object :

  • Required
    apiVersion string

    Specifies the version of the API that incorporates this endpoint.

    Example : 2.0
  • 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 : You can add any text here
  • Required
    data object
    • Required
      item object
      • Required
        feePriority string

        Represents the fee priority of the automation, whether it is "slow", "standard" or "fast".

        Example : standard
        Possible Values : slow standard fast
      • Required
        recipients array

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

        • Required
          address string

          Defines the destination address.

          Example : 0x1316bea88fb7cd4ccc4a57e2f9f4f43d1a86ee59
        • Required
          amount string

          Defines the amount sent to the destination address.

          Example : 0.0023
      • Required
        senders object

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

        • Required
          address string

          Defines the sender's public address.

          Example : 0x8798d11a96a2822ae60275f3a0798a2542912a10
      • Required
        transactionRequestStatus string

        Defines the status of the transaction request, e.g. "created, "await_approval", "pending", "prepared", "signed", "broadcasted", "success", "failed", "rejected", mined".

        Example : created
        Possible Values : created await-approval pending prepared signed broadcasted success failed rejected mined
Try it out

Request Example

POST
https://rest.cryptoapis.io/v2/wallet-as-a-service/wallets/609e221675d04500068718dc/ethereum/network/addresses/0x6f61e3c2fbb8c8be698bd0907ba6c04b62800fe5/transaction-requests
Headers
Host: https://rest.cryptoapis.io/v2
Content-Type: application/json
X-API-Key: my-api-key

Request Body
{
    "context": "",
    "data": {
        "item": {
            "amount": "0.2",
            "feePriority": "slow",
            "toAddress": "0xc065b539490f81b6c297c37b1925c3be2f190732"
        }
    }
}

Response Example

{
    "apiVersion": "2.0",
    "requestId": "601c1710034ed6d407996b30",
    "context": "You can add any text here",
    "data": {
        "item": {
            "feePriority": "standard",
            "recipients": [
                {
                    "address": "0x1316bea88fb7cd4ccc4a57e2f9f4f43d1a86ee59",
                    "amount": "0.0023"
                }
            ],
            "senders": {
                "address": "0x8798d11a96a2822ae60275f3a0798a2542912a10"
            },
            "transactionRequestStatus": "created"
        }
    }
}