Through this endpoint customers can broadcast transactions that have been already signed locally. Instead of using a node for broadcasting a signed transaction users can use this endpoint. We then keep the user posted about the status by sending you a callback with a success or failure status.
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.
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 signed transaction's specific hex.
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 unique identifier of a transaction, i.e. it could be transactionId
in UTXO-based protocols like Bitcoin, and transaction hash
in Ethereum blockchain.
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.
Defines the unique ID of the specific transaction, i.e. its identification number.
API Key
{
"context": "yourExampleString",
"data": {
"item": {
"callbackSecretKey": "yourSecretString",
"callbackUrl": "https://example.com",
"signedTransactionHex": "0xf86a22827d00831e8480941b85a43e2e7f52e766ddfdfa2b901c42cb1201be8801b27f33b807c0008029a084ccbf02b27e0842fb1eda7a187a5589c3759be0e969e0ca989dc469a5e5e394a02e111e1156b197f1de4c1d9ba4af26e50665ea6d617d05b3e4047da12b915e69"
}
}
}
{
"apiVersion": "2023-04-25",
"requestId": "601c1710034ed6d407996b30",
"context": "yourExampleString",
"data": {
"item": {
"transactionId": "347d96855d41b77f1e23048fff11c18e9fe699ee69b0b402338f34189734e0a2"
}
}
}
{
"apiVersion": "2021-03-20",
"referenceId": "6038d09050653d1f0e40584c",
"idempotencyKey": "e55bf7a4a7188855f1c27541a6c387d04cc3b22ee34d1304b0e6ecad61c9906c",
"data": {
"product": "BLOCKCHAIN_TOOLS",
"event": "BROADCAST_TRANSACTION_SUCCESS",
"item": {
"blockchain": "Bitcoin/Ethereum (whichever applicable)",
"network": "Testnet/Mainnet (whichever applicable)",
"transactionId": "347d96855d41b77f1e23048fff11c18e9fe699ee69b0b402338f34189734e0a2"
}
}
}