Through this endpoint customers can create a new transaction from address for coins specifically, which will transfer over the entire available amount.
Defines the source address.
Represents the specific blockchain protocol name, e.g. Ethereum, Bitcoin, etc.
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.
Represents the sender's specific and unique Wallet ID of the sender.
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.
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.
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.
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
.
Represents the fee priority of the automation, whether it is "slow", "standard" or "fast".
Represents an optional note to add a free text in, explaining or providing additional detail on the transaction request.
Defines the specific recipient address for the transaction.
Specifies the version of the API that incorporates this endpoint.
Defines the ID of the request. The requestId
is generated by Crypto APIs and it's unique for every request.
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.
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.
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
.
Represents the fee priority of the automation, whether it is "slow", "standard" or "fast".
Represents an optional note to add a free text in, explaining or providing additional detail on the transaction request.Optional Transaction note with additional details
Defines the destination for the transaction, i.e. the recipient(s).
Defines the destination address.
Defines the amount sent to the destination address.
Details about the sender
Defines the sender's public address.
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.
Defines the status of the transaction, e.g. "created, "await_approval", "pending", "prepared", "signed", "broadcasted", "success", "failed", "rejected", mined".
Specifies the version of the API that incorporates this endpoint.
Represents a unique identifier that serves as reference to the specific request which prompts a callback, e.g. Blockchain Events Subscription, Blockchain Automation, etc.
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.
Specifies all data, as attributes, included into the callback notification, which depends on the event
.
Represents the Crypto APIs 2.0 product which sends the callback.
Defines the specific event, for which a callback subscription is set.
Defines an item
as one result.
Represents the specific blockchain protocol name, e.g. Ethereum, Bitcoin, etc.
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", "mordor" are test networks.
The required number of approvals needed to approve the transaction.
The required number of rejections needed to reject the transaction.
The current number of approvals given for the transaction.
The current number of rejections given for the transaction.
API Key
{
"context": "yourExampleString",
"data": {
"item": {
"callbackSecretKey": "yourSecretString",
"callbackUrl": "https://example.com",
"feePriority": "standard",
"note": "yourAdditionalInformationhere",
"recipientAddress": "0xc6d46aba0c6e2eb6358c4e24804158cc4d847922"
}
}
}
{
"apiVersion": "2023-04-25",
"requestId": "601c1710034ed6d407996b30",
"context": "yourExampleString",
"data": {
"item": {
"callbackSecretKey": "yourSecretKey",
"callbackUrl": "https://example.com",
"feePriority": "standard",
"note": "yourExampleStringHere",
"recipients": [
{
"address": "0xc065b539490f81b6c297c37b1925c3be2f190732",
"amount": "0.123"
}
],
"senders": {
"address": "0x0902a667d6a3f287835e0a4593cae4167384abc6"
},
"transactionRequestId": "6017dd02a309213863be9e55",
"transactionRequestStatus": "created"
}
}
}
{
"apiVersion": "2021-03-20",
"referenceId": "6038d09050653d1f0e40584c",
"idempotencyKey": "e55bf7a4a7188855f1c27541a6c387d04cc3b22ee34d1304b0e6ecad61c9906c",
"data": {
"product": "WALLET_AS_A_SERVICE",
"event": "TRANSACTION_REQUEST_APPROVAL",
"item": {
"blockchain": "Bitcoin/Ethereum (whichever applicable)",
"network": "Testnet/Mainnet (whichever applicable)",
"requiredApprovals": 2,
"requiredRejections": 2,
"currentApprovals": 1,
"currentRejections": 0
}
}
}