Broadcast Locally Signed Transaction
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.
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
-
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.
-
OptionalcallbackUrl 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
. -
RequiredsignedTransactionHex string
Represents the signed transaction's specific hex.
-
-
Response schema
Content-Type: application/json
The resource has been successfully submitted.
Object :
-
RequiredapiVersion string
Specifies the version of the API that incorporates this endpoint.
Example : 2023-04-25 -
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
-
RequiredtransactionId string
Represents the unique identifier of a transaction, i.e. it could be
transactionId
in UTXO-based protocols like Bitcoin, and transactionhash
in Ethereum blockchain.Example : 347d96855d41b77f1e23048fff11c18e9fe699ee69b0b402338f34189734e0a2
-
-
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_TOOLS -
Requiredevent string
Defines the specific event, for which a callback subscription is set.
Example : BROADCAST_TRANSACTION_SUCCESS -
Requireditem object
Defines an
item
as one result.-
Requiredblockchain string
Represents the specific blockchain protocol name, e.g. Ethereum, Bitcoin, etc.
Example : Bitcoin/Ethereum (whichever applicable) -
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/Mainnet (whichever applicable) -
RequiredtransactionId string
Defines the unique ID of the specific transaction, i.e. its identification number.
Example : 347d96855d41b77f1e23048fff11c18e9fe699ee69b0b402338f34189734e0a2
-
-