Create Fungible Tokens Transaction Request From Address
Through this endpoint users can make a single token transaction.
Path Parameters
-
Requiredblockchain string
Represents the specific blockchain protocol name, e.g. Ethereum, Binance Smart Chain, 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", "sepolia" are test networks.
-
RequiredsenderAddress string
Defines the specific source address for the transaction.
-
RequiredvaultId string
Defines the unique ID of the Vault.
Query Paramaters
-
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.
-
RequiredfeePriority string
Represents the fee priority of the automation, whether it is "slow", "standard" or "fast".
-
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
Defines the specific token identifier. For Ethereum-based transactions - the
contract
.
-
-
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 : 2024-05-09 -
RequiredrequestId string
Defines the ID of the request. The
requestId
is generated by Vaultody 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
-
RequiredfeePriority string
Represents the fee priority of the automation, whether it is "slow", "standard" or "fast".
Example : fast -
Optionalnote string
Represents an optional note to add a free text in, explaining or providing additional detail on the transaction request.
Example : yourAdditionalInformationhere -
Requiredrecipients array
Defines the destination for the transaction, i.e. the recipient(s).
Example : 0x1316bea88fb7cd4ccc4a57e2f9f4f43d1a86ee59-
Requiredaddress string
Defines the destination address.
Example : 0xc6d46aba0c6e2eb6358c4e24804158cc4d847922 -
Requiredamount string
Defines the amount sent to the destination address.
Example : 0.2
-
-
Requiredsenders object
Defines details about the source, i.e. the sender.
-
Requiredaddress string
Defines the sender's public address.
Example : 0x0902a667d6a3f287835e0a4593cae4167384abc6
-
-
RequiredtokenTypeSpecificData object object One Ofobject
-
RequiredcontractAddress string
Defines the contract address in the blockchain for an ERC20 token.
Example : 0x534bD102153EF199abAe8296a2FaE4599fC44Cdc
-
-
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 : 6038d09050653d1f0e40584c
-
-