Sign and Broadcast Transaction
Sign & Broadcast transaction enables communication with any arbitrary smart contract of the target blockchain. You can construct a transaction that performs a complex task and this endpoint will sign the transaction, add the signature and broadcast it to chain. It can be used to call smart contract functions like mint tokens and even deploy new smart contracts.
| Status | Definition |
|---|---|
| Pending | The request is pending approval due to a policy applied to the wallet. |
| Executing | The request is approved and is in the process of being executed. note this status is only set for a short time between pending and broadcasted. |
| Broadcasted | The transaction has been successfully written to the mempool. |
| Confirmed | The transaction has been confirmed on-chain by our indexing pipeline. |
| Failed | Indicates either a system failure to complete the request or the transaction failed on chain. |
| Rejected | The request has been rejected by a policy approval action. |
for reading from a “view” function on EVM chains, please use Read Contract endpoint.
Authentication
✅ Organization User (CustomerEmployee)✅ Delegated User (
EndUser)✅ Service Account
Required Permissions
Wallets:Transactions:Create: Always requiredFeeSponsors:Use: Required if feeSponsorId is specified.Authorizations
Bearer Token: Used to authenticate API requests. More details how to generate the token: Authentication flows
User Action Signature: Used to sign the change-inducing API requests. More details how to generate the token: User Action Signing flows
Path Parameters
Wallet id.
1 - 64Body
- Transaction
- PSBT
- SignDocDirect
- EVM Sponsored transaction
- Function Call
- Canton Transfer Preapproval
- <Deprecated> EVM Transaction
- <Deprecated> EVM EIP-1559
- Create Solana Nonce Accounts
- AcceptInboundAsset
Signs an unsigned transaction and broadcasts it to chain. For EVM transactions, you may use JSON objects:
For Starknet transactions, you may use invocation request objects (https://github.com/starkware-libs/starknet-specs/blob/v0.8.1/api/starknet_api_openrpc.json#L2621):
For Concordium transactions, you may use JSON objects (from https://github.com/Concordium/concordium-node-sdk-js/blob/sdk/12.0.0-alpha.3/packages/sdk/src/transactions/Transaction.ts#L102)
Transaction The unsigned hex encoded transaction or JSON transactions for compatible networks.
^(0x)?([0-9a-fA-F][0-9a-fA-F])*$Response
Success
Transaction id.
1 - 64^tx-[a-z0-9]{5}-[a-z0-9]{5}-[a-z0-9]{14,16}$"tx-583hu-sp2p7-slvb9nqpa3hd8bus"
Wallet id.
1 - 64^wa-[a-z0-9]{5}-[a-z0-9]{5}-[a-z0-9]{14,16}$"wa-5pfuu-9euek-h0odgb6snva8ph3k"
Algorand, AlgorandTestnet, Aptos, AptosTestnet, ArbitrumOne, ArbitrumSepolia, ArcTestnet, AvalancheC, AvalancheCFuji, BabylonGenesis, BabylonTestnet5, Base, BaseSepolia, Berachain, BerachainBepolia, Bitcoin, BitcoinSignet, BitcoinTestnet4, BitcoinCash, Bob, BobSepolia, Bsc, BscTestnet, Canton, CantonTestnet, Cardano, CardanoPreprod, Concordium, ConcordiumTestnet, Celo, CeloAlfajores, Codex, CodexSepolia, CosmosHub4, CosmosIcsTestnet, Dogecoin, DogecoinTestnet, Ethereum, EthereumClassic, EthereumClassicMordor, EthereumSepolia, EthereumHoodi, FlareC, FlareCCoston2, FlowEvm, FlowEvmTestnet, Hedera, HederaTestnet, Ink, InkSepolia, InternetComputer, Ion, IonTestnet, Iota, IotaTestnet, Kusama, KusamaAssetHub, Litecoin, LitecoinTestnet, Movement, MovementTestnet, Near, NearTestnet, Optimism, OptimismSepolia, Origyn, Plasma, PlasmaTestnet, Plume, PlumeSepolia, Paseo, PaseoAssetHub, Polkadot, PolkadotAssetHub, Polygon, PolygonAmoy, Polymesh, PolymeshTestnet, Race, RaceSepolia, Rayls, RaylsTestnet, Robinhood, RobinhoodSepolia, SeiAtlantic2, SeiPacific1, Solana, SolanaDevnet, Sonic, SonicTestnet, Starknet, StarknetSepolia, Stellar, StellarTestnet, Sui, SuiTestnet, Tezos, TezosGhostnet, TezosShadownet, Tempo, TempoModerato, Tsc, TscTestnet1, Ton, TonTestnet, Tron, TronNile, Westend, WestendAssetHub, Xdc, XdcApothem, XLayer, XLayerSepolia, XrpLedger, XrpLedgerTestnet The user who initiated the request.
Signs an unsigned transaction and broadcasts it to chain. For EVM transactions, you may use JSON objects:
For Starknet transactions, you may use invocation request objects (https://github.com/starkware-libs/starknet-specs/blob/v0.8.1/api/starknet_api_openrpc.json#L2621):
For Concordium transactions, you may use JSON objects (from https://github.com/Concordium/concordium-node-sdk-js/blob/sdk/12.0.0-alpha.3/packages/sdk/src/transactions/Transaction.ts#L102)
- Transaction
- PSBT
- SignDocDirect
- EVM Sponsored transaction
- Function Call
- Canton Transfer Preapproval
- <Deprecated> EVM Transaction
- <Deprecated> EVM EIP-1559
- Create Solana Nonce Accounts
- AcceptInboundAsset
- Solana CCTP Burn
- Offer Settlement
- Account Activation
- Transaction Cancellation
- Transaction Speed Up
Pending, Executing, Broadcasted, Confirmed, Failed, Rejected 1 - 64^ap-[a-z0-9]{5}-[a-z0-9]{5}-[a-z0-9]{14,16}$"ap-2a9in-tt2a1-983lho480p35ejd0"
The id of the replacement transaction (cancel or speed-up) issued for this transaction.
Structured representation of the data used to construct the signature (e.g. nonce, gas parameters). Shape is blockchain specific.