Jump to
Ctrl
+
/

Create Fungible Tokens Transaction Request From Address

POST
/vaults/{vaultId}/{blockchain}/{network}/addresses/{senderAddress}/token-transaction-requests

Through this endpoint users can make a single token transaction.


To have an operational callback subscription, you need to first verify a domain for the Callback URL. Please see more information on Callbacks here.

Vaultody will notify the user only when the event occurs. There are cases when the specific event doesn't happen at all, or takes a long time to do so. A callback notification will not be sent if the event does not or cannot occur, or will take long time to occur.

Path Parameters

blockchain string Required

Represents the specific blockchain protocol name, e.g. Ethereum, Binance Smart Chain, etc.

network string Required

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

senderAddress string Required

Defines the specific source address for the transaction.

vaultId string Required

Defines the unique ID of the Vault.

Query Parameters

context string Optional

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

context string Optional

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.

data object Required
item object Required
amount string Required

Represents the specific amount of the transaction.

feePriority string Required

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

note string Optional

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

recipientAddress string Required

Defines the specific recipient address for the transaction.

tokenIdentifier string Required

Defines the specific token identifier. For Ethereum-based transactions - the contract.

Response Schema

apiVersion string Required

Specifies the version of the API that incorporates this endpoint.

2024-05-09
requestId string Required

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

601c1710034ed6d407996b30
context string Optional

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.

yourExampleString
data object Required
item object Required
feePriority string Required

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

fast
note string Optional

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

yourAdditionalInformationhere
recipients array Items (object) Required

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

address string Required

Defines the destination address.

0xc6d46aba0c6e2eb6358c4e24804158cc4d847922
amount string Required

Defines the amount sent to the destination address.

0.2
senders object Required

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

address string Required

Defines the sender's public address.

0x0902a667d6a3f287835e0a4593cae4167384abc6
tokenTypeSpecificData object Required

Represents the specific token data which depends on its type - if it is a Coin or Token.

contractAddress string Required

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

0x534bD102153EF199abAe8296a2FaE4599fC44Cdc
transactionRequestId string Required

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.

6038d09050653d1f0e40584c
Was this page helpful?
Yes
No
Powered by
Language
URL

{
    "apiVersion": "2024-05-09",
    "requestId": "601c1710034ed6d407996b30",
    "context": "yourExampleString",
    "data": {
        "item": {
            "feePriority": "fast",
            "note": "yourAdditionalInformationhere",
            "recipients": [
                {
                    "address": "0xc6d46aba0c6e2eb6358c4e24804158cc4d847922",
                    "amount": "0.2"
                }
            ],
            "senders": {
                "address": "0x0902a667d6a3f287835e0a4593cae4167384abc6"
            },
            "tokenTypeSpecificData": {
                "contractAddress": "0x534bD102153EF199abAe8296a2FaE4599fC44Cdc"
            },
            "transactionRequestId": "6038d09050653d1f0e40584c"
        }
    }
}