Through this endpoint customers can add Automatic Tokens forwardings to an already existing fromAddress
. Unlike the "Create Automatic Tokens Forwarding" endpoint, where the fromAddress
is generated each time, with this endpoint customers can add an automation from another token to one and the same fromAddress
.
The fromAddress
can be used as a deposit address. Any funds received by this address will be automatically forwarded to toAddress
based on what the customer has set for the automation. The toAddress
is essentially the main address and destination for the automatic tokens forwarding.
There is also a minimumTransferAmount
which only when reached will then trigger the forwarding. Through this the customer can save from fees.
Moreover, feePriority
can be also set, which defines how quickly to move the tokens once they are received. The higher priority, the larger the fee will be. It can be "SLOW", "STANDARD" or "FAST".
For this automatic forwarding the customer can set a callback subscription.
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 network like "testnet" is the test network.
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 number of confirmations, i.e. the amount of blocks that have been built on top of this block.
Represents the fee priority of the automation, whether it is "SLOW", "STANDARD" or "FAST".
Represents the hash of the address that forwards the tokens.
Represents the minimum transfer amount of the currency in the fromAddress
that can be allowed for an automatic forwarding.
Represents the hash of the address the currency is forwarded to.
Represents the specific propertyId
of the token data that will be forwarded.
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 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 number of confirmations, i.e. the amount of blocks that have been built on top of this block.
Defines the specific time/date when the automatic forwarding was created in Unix Timestamp.
Represents the specific fee address, which is always automatically generated. Users must fund it.
Represents the fee priority of the automation, whether it is "SLOW", "STANDARD" or "FAST".
Represents the hash of the address that forwards the tokens.
Represents the minimum transfer amount of the tokens in the fromAddress
that can be allowed for an automatic forwarding.
Represents a unique ID used to reference the specific callback subscription.
Represents the hash of the address the tokens are forwarded to.
Defines the propertyId
of the Omni Layer token.
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" are test networks.
Represents the hash of the address that provides the tokens.
Represents the hash of the address to forward the tokens to.
Represents the amount of the fee spent for the tokens to be forwarded.
Represents the unit of the fee spent for the tokens to be forwarded, e.g. BTC.
Defines the unique Transaction ID that triggered the token forwarding.
Defines the unique Transaction ID that forwarded the tokens.
Defines the type of token sent with the transaction, e.g. ERC 20.
Specifies the name of the token.
Specifies an identifier of the token, where up to five alphanumeric characters can be used for it.
Defines how many decimals can be used to break the token.
Defines the amount of tokens sent with the confirmed transaction.
Defines the address of the contract.
API Key
{
"context": "yourExampleString",
"data": {
"item": {
"callbackSecretKey": "yourSecretString",
"callbackUrl": "https://example.com",
"confirmationsCount": 3,
"feePriority": "standard",
"fromAddress": "mizRduUBKEbJ6uzYJUegPh78gEGgM3WjAr",
"minimumTransferAmount": "0.00001",
"toAddress": "mnumE76iEKN47bUsdni85oped5D1fRwKWi",
"tokenData": {
"propertyId": 2
}
}
}
}
{
"apiVersion": "2023-04-25",
"requestId": "601c1710034ed6d407996b30",
"context": "yourExampleString",
"data": {
"item": {
"callbackUrl": "https://example.com",
"confirmationsCount": 3,
"createdTimestamp": 1611238648,
"feeAddress": "mojjR51gMXLJ4B3SBPhEXXRFDX7U5UWXNQ",
"feePriority": "standard",
"fromAddress": "mizRduUBKEbJ6uzYJUegPh78gEGgM3WjAr",
"minimumTransferAmount": "0.0001",
"referenceId": "6017dd02a309213863be9e55",
"toAddress": "mnumE76iEKN47bUsdni85oped5D1fRwKWi",
"tokenData": {
"propertyId": 2
}
}
}
}
{
"apiVersion": "2021-03-20",
"referenceId": "6038d09050653d1f0e40584c",
"idempotencyKey": "e55bf7a4a7188855f1c27541a6c387d04cc3b22ee34d1304b0e6ecad61c9906c",
"data": {
"product": "BLOCKCHAIN_AUTOMATIONS",
"event": "TOKENS_FORWARDING_SUCCESS",
"item": {
"blockchain": "bitcoin",
"network": "testnet",
"fromAddress": "mySJoZ6wsjrKXZQRWpGoeBW5KkdKGL79Xz",
"toAddress": "mmd963W1fECjLyaDCHcioSCZYHkRwjkGST",
"spentFeesAmount": "0.00013601",
"spentFeesUnit": "BTC",
"triggerTransactionId": "6ed1f1c8f2887a78ee8c45a975d928ca63eafc7b63def56324606ddd3cc9854f",
"forwardingTransactionId": "b15ab5bbaf5107d551ae1b50181f4c55959205c4ff843e3c10d86d00e690fc72",
"tokenType": "OMNI",
"token": {
"name": "Tether USD",
"symbol": "USDT",
"decimals": "6",
"amount": "0.00039",
"contractAddress": "0xdac17f958d2ee523a2206206994597c13d831ec7"
}
}
}
}