Broadcast Transaction
Warning: This API has been deprecated. Please use Wallets. Contact your sales representative if you require additional blockchain support.
POST /public-keys/transactions
Broadcast transaction enables communication with any arbitrary smart contract by replicating the native transaction protocol fields in the body of the request. It can be used to make native payments, call smart contract functions, and even deploy new smart contracts. Note for reading from a "view" function on EVM chains, please use Call Read Function.
Currently, only EVM compatible chains are supported. We plan to add additional chain support in the future. Please don't hesitate to contact us if you need support for a non-EVM chain.
User action signature required. See User Action Signing for more information.
Request headers required. See Request Headers for more information.
Authentication required. See Authentication Headers for more information.
Required Permissions
Name | Conditions |
---|---|
| Always Required |
Request body
The following fields are common to all templateKinds:
Request body fields | Required/Optional | Description | Type |
---|---|---|---|
| Required | Unique identifier of the | String |
| Required | Enumerated type representing the Blockchain network from the list found here. | Enumerated Type |
| Required | Enumerated type representing the Blockchain transaction template that dictates the remaining acceptable fields. Currently, the only supported value is " | Enumerated Type |
For details on specific templateKinds, please see the chain specific sub pages underneath this article in the left hand navigation.
Request example
Response
Response example
Status begins as Initiated
and changes to Executed
once broadcast to the mempool. Use GetTransactionById to query for updated status and to retrieve a blockchain transaction hash.
Last updated