New confirmed coins transactions and 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.
Path Parameters
-
Requiredblockchain string
Represents the specific blockchain protocol name, e.g. Ethereum, Bitcoin, 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", "ropsten" are test networks.
Query parameters
-
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
-
Requiredaddress string
Represents the address of the transaction, per which the result is returned.
-
OptionalallowDuplicates boolean
Specifies a flag that permits or denies the creation of duplicate addresses.
-
OptionalcallbackSecretKey string
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.
-
RequiredcallbackUrl string
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
. -
RequiredconfirmationsCount integer
Represents the number of confirmations, i.e. the amount of blocks that have been built on top of this block.
-
-
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 : 2021-03-20 -
RequiredrequestId string
Defines the ID of the request. The
requestId
is generated by Crypto APIs 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
-
Requiredaddress string
Represents the address of the transaction, per which the result is returned.
Example : 15XyNC88pujwuuur8DCsXBCfEhJJMzHayU -
RequiredcallbackSecretKey string
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.
Example : yourSecretKey -
RequiredcallbackUrl string
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
.Example : https://example.com -
RequiredconfirmationsCount integer
Represents the number of confirmations, i.e. the amount of blocks that have been built on top of this block.
Example : 3 -
RequiredcreatedTimestamp integer
Defines the specific time/date when the subscription was created in Unix Timestamp.
Example : 1611238648 -
RequiredeventType string
Defines the type of the specific event available for the customer to subscribe to for callback notification.
Example : ADDRESS_COINS_TRANSACTION_CONFIRMED_EACH_CONFIRMATION -
RequiredisActive boolean
Defines whether the subscription is active or not. Set as boolean.
Example : True -
RequiredreferenceId string
Represents a unique ID used to reference the specific callback subscription.
Example : bc243c86-0902-4386-b30d-e6b30fa1f2aa
-
-
Callback parameters Method : POST
Content-Type : application/json
Object :
-
RequiredapiVersion string
Specifies the version of the API that incorporates this endpoint.
Example : 2021-03-20 -
RequiredreferenceId string
Represents a unique identifier that serves as reference to the specific request which prompts a callback, e.g. Blockchain Events Subscription, Blockchain Automation, etc.
Example : 6038d09050653d1f0e40584c -
RequiredidempotencyKey string
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.
Example : e55bf7a4a7188855f1c27541a6c387d04cc3b22ee34d1304b0e6ecad61c9906c -
Requireddata object
Specifies all data, as attributes, included into the callback notification, which depends on the
event
.-
Requiredproduct string
Represents the Crypto APIs 2.0 product which sends the callback.
Example : BLOCKCHAIN_EVENTS -
Requiredevent string
Defines the specific event, for which a callback subscription is set.
Example : ADDRESS_COINS_TRANSACTION_CONFIRMED_EACH_CONFIRMATION -
Requireditem object
Defines an
item
as one result.-
Requiredblockchain string
Represents the specific blockchain protocol name, e.g. Ethereum, Bitcoin, etc.
Example : bitcoin -
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", "ropsten", "rinkeby" are test networks.
Example : testnet -
Requiredaddress string
Defines the specific address to which the transaction has been sent.
Example : 15282N4BYEwYh3j1dTgJu64Ey5qWn9Po9F -
RequiredminedInBlock object
Refers to the specific block the transaction was mined in.
-
Requiredheight integer
Defines the number of blocks in the blockchain preceding this specific block.
Example : 667754 -
Requiredhash string
Represents the hash of the block's header, i.e. an output that has a fixed length.
Example : dfe45f6724b550c281107ffaa5880cb280878fb4dbaa742aa21449f3d2340c13 -
Requiredtimestamp integer
Defines the exact date/time when this transaction was mined in seconds since Unix Epoch time.
Example : 1610365314
-
-
RequiredtransactionId string
Defines the unique ID of the specific transaction, i.e. its identification number.
Example : cbd3dea703bd2bc78bca69ee61ca14e6ffcdd809d07ebbc3b8fea3c30ea38f33 -
RequiredcurrentConfirmations integer
Defines the number of currently received confirmations for the transaction.
Example : 8 -
RequiredtargetConfirmations integer
Defines the number of confirmation transactions requested as callbacks, i.e. the system can notify till the n-th confirmation.
Example : 12 -
Requiredamount string
Defines the amount of coins sent with the confirmed transaction.
Example : 0.0611 -
Requiredunit string
Defines the unit of the transaction, e.g. BTC.
Example : BTC -
Requireddirection string
Defines whether the transaction is "incoming" or "outgoing".
Example : incoming
-
-