Skip to main content
POST
Used for the standard (gasless: false) flow: the user signs the raw transaction from the /v1/buildTx response, and you submit the signed transaction here. For the gasless flow, see Execute instead.

Body

string
required
The txId from the non-gasless /v1/buildTx response.
integer
required
Chain ID to broadcast on.
string | object[]
required
The signed transaction payload. For most EVM steps this is a raw signed-transaction hex string. For HyperLiquid it’s an array of { message, primaryType, signatureChainId, signature, account } typed-data signature objects instead.

Response

string
"success" or an error status.
string
On-chain transaction hash. Present when status is "success".
string
Error details. Present when status is not "success".
Once submitted, poll /v1/status with the resulting txnHash and chainId to track settlement - especially for cross-chain bridges.
Last modified on July 29, 2026