Through this endpoint the customer can obtain a list of their callback subscriptions for the available Blockchain events.
Currently Crypto APIs 2.0 offers certain Blockchain event endpoints which allow the user to subscribe for one/a few/all and receive callback notifications when the specific event occurs.
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 a 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.
Defines how many items should be returned in the response per page basis.
The starting index of the response items, i.e. where the response should start listing the returned items.
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.
Defines how many items should be returned in the response per page basis.
The starting index of the response items, i.e. where the response should start listing the returned items.
Defines the total number of items returned in the response.
Represents the address of the transaction.
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.
Defines the specific time/date when the subscription was created in Unix Timestamp.
Represents the deactivation reason details, available when a blockchain event subscription has status isActive - false.
Defines the deactivation reason as a message.
Represents the time of the subscription deactivation.
Defines the type of the specific event available for the customer to subscribe to for callback notification.
Defines whether the subscription is active or not. Set as boolean.
Represents a unique ID used to reference the specific callback subscription.
Represents the unique identification string that defines the transaction.
API Key
{
"apiVersion": "2023-04-25",
"requestId": "601c1710034ed6d407996b30",
"context": "yourExampleString",
"data": {
"limit": 50,
"offset": 0,
"total": 100,
"items": [
{
"address": "tb1qtm44m6xmuasy4sc7nl7thvuxcerau2dfvkkgsc",
"callbackSecretKey": "yourSecretKey",
"callbackUrl": "https://example.com",
"confirmationsCount": 5,
"createdTimestamp": 1966238648,
"deactivationReasons": [
{
"reason": "maximum_retry_attempts_reached",
"timestamp": 1642102581
}
],
"eventType": "BLOCK_MINED",
"isActive": true,
"referenceId": "bc243c86-0902-4386-b30d-e6b30fa1f2aa",
"transactionId": "742b4a8d54a663d372fa16abf74093595ae6fc950f2fa2bb7388c7f4d061d7b8"
}
]
}
}