Jump to
Ctrl
+
/

New Confirmed Coins Transactions And Each Confirmation

POST
/blockchain-events/{blockchain}/{network}/subscriptions/address-coins-transactions-confirmed-each-confirmation

Through this endpoint customers can create callback subscriptions for a specific event. In this case the event is when there are new incoming or outgoing confirmed transactions for coins from/to the customer's address with also a response at each confirmation the transaction has received until the specified confirmations limit is reached. By creating this subscription the user will be notified by Crypto APIs 2.0 when that event occurs. The information is returned per specified address.

Being confirmed means that the transactions are verified by miners and added to the next block. This endpoint refers to coins transactions only, not tokens.


For UTXO-based protocols like Bitcoin, a transaction could have multiple inputs and outputs, which means the address could be both sender and recipient. Here is how we inform you on that.

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

Crypto APIs 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, Bitcoin, 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.

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
address string Required

Represents the address of the transaction, per which the result is returned.

allowDuplicates boolean Optional

Specifies a flag that permits or denies the creation of duplicate addresses.

Default : false
callbackSecretKey string Optional

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.

callbackUrl string Required

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.

confirmationsCount integer Required

Represents the number of confirmations, i.e. the amount of blocks that have been built on top of this block.

Response Schema

apiVersion string Required

Specifies the version of the API that incorporates this endpoint.

2023-04-25
requestId string Required

Defines the ID of the request. The requestId is generated by Crypto APIs 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
address string Required

Represents the address of the transaction, per which the result is returned.

15XyNC88pujwuuur8DCsXBCfEhJJMzHayU
callbackSecretKey string Required

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.

yourSecretKey
callbackUrl string Required

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.

https://example.com
confirmationsCount integer Required

Represents the number of confirmations, i.e. the amount of blocks that have been built on top of this block.

3
createdTimestamp integer Required

Defines the specific time/date when the subscription was created in Unix Timestamp.

1611238648
eventType string Required

Defines the type of the specific event available for the customer to subscribe to for callback notification.

ADDRESS_COINS_TRANSACTION_CONFIRMED_EACH_CONFIRMATION
isActive boolean Required

Defines whether the subscription is active or not. Set as boolean.

true
referenceId string Required

Represents a unique ID used to reference the specific callback subscription.

bc243c86-0902-4386-b30d-e6b30fa1f2aa

Callback parameters

apiVersion string Required

Specifies the version of the API that incorporates this endpoint.

2021-03-20
referenceId string Required

Represents a unique identifier that serves as reference to the specific request which prompts a callback, e.g. Blockchain Events Subscription, Blockchain Automation, etc.

6038d09050653d1f0e40584c
idempotencyKey string Required

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.

e55bf7a4a7188855f1c27541a6c387d04cc3b22ee34d1304b0e6ecad61c9906c
data object Required

Specifies all data, as attributes, included into the callback notification, which depends on the event.

product string Required

Represents the Crypto APIs 2.0 product which sends the callback.

BLOCKCHAIN_EVENTS
event string Required

Defines the specific event, for which a callback subscription is set.

ADDRESS_COINS_TRANSACTION_CONFIRMED_EACH_CONFIRMATION
item object Required

Defines an item as one result.

blockchain string Required

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

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

testnet
address string Required

Defines the specific address to which the transaction has been sent.

15282N4BYEwYh3j1dTgJu64Ey5qWn9Po9F
minedInBlock object Required

Refers to the specific block the transaction was mined in.

height integer Required

Defines the number of blocks in the blockchain preceding this specific block.

667754
hash string Required

Represents the hash of the block's header, i.e. an output that has a fixed length.

dfe45f6724b550c281107ffaa5880cb280878fb4dbaa742aa21449f3d2340c13
timestamp integer Required

Defines the exact date/time when this transaction was mined in seconds since Unix Epoch time.

1610365314
transactionId string Required

Defines the unique ID of the specific transaction, i.e. its identification number.

cbd3dea703bd2bc78bca69ee61ca14e6ffcdd809d07ebbc3b8fea3c30ea38f33
currentConfirmations integer Required

Defines the number of currently received confirmations for the transaction.

8
targetConfirmations integer Required

Defines the number of confirmation transactions requested as callbacks, i.e. the system can notify till the n-th confirmation.

12
amount string Required

Defines the amount of coins sent with the confirmed transaction.

0.0611
unit string Required

Defines the unit of the transaction, e.g. BTC.

BTC
direction string Required

Defines whether the transaction is "incoming" or "outgoing".

incoming

Credits Cost : 400 Credits for 1 Results

Was this page helpful?
Yes
No
Powered by
Language
URL

{
    "apiVersion": "2023-04-25",
    "requestId": "601c1710034ed6d407996b30",
    "context": "yourExampleString",
    "data": {
        "item": {
            "address": "15XyNC88pujwuuur8DCsXBCfEhJJMzHayU",
            "callbackSecretKey": "yourSecretKey",
            "callbackUrl": "https://example.com",
            "confirmationsCount": 3,
            "createdTimestamp": 1611238648,
            "eventType": "ADDRESS_COINS_TRANSACTION_CONFIRMED_EACH_CONFIRMATION",
            "isActive": true,
            "referenceId": "bc243c86-0902-4386-b30d-e6b30fa1f2aa"
        }
    }
}
{
    "apiVersion": "2021-03-20",
    "referenceId": "6038d09050653d1f0e40584c",
    "idempotencyKey": "e55bf7a4a7188855f1c27541a6c387d04cc3b22ee34d1304b0e6ecad61c9906c",
    "data": {
        "product": "BLOCKCHAIN_EVENTS",
        "event": "ADDRESS_COINS_TRANSACTION_CONFIRMED_EACH_CONFIRMATION",
        "item": {
            "blockchain": "bitcoin",
            "network": "testnet",
            "address": "15282N4BYEwYh3j1dTgJu64Ey5qWn9Po9F",
            "minedInBlock": {
                "height": 667754,
                "hash": "dfe45f6724b550c281107ffaa5880cb280878fb4dbaa742aa21449f3d2340c13",
                "timestamp": 1610365314
            },
            "transactionId": "cbd3dea703bd2bc78bca69ee61ca14e6ffcdd809d07ebbc3b8fea3c30ea38f33",
            "currentConfirmations": 8,
            "targetConfirmations": 12,
            "amount": "0.0611",
            "unit": "BTC",
            "direction": "incoming"
        }
    }
}