Skip to main content
POST
After building a transaction with /v1/buildTx (or /v1/bundle/buildTx) and signing the resulting calldata client-side, submit it here for the DZap relay to broadcast on-chain.

Body

txId
string
required
The txnId returned for the step in the build-transaction response.
chainId
integer
required
Chain ID the transaction should be broadcast on.
txData
string | object[]
required
The signed transaction payload. For most EVM steps this is a raw signed-transaction hex string. For HyperLiquid steps it’s an array of { message, primaryType, signatureChainId, signature, account } typed-data signature objects instead.

Response

status
string
"success" or "error".
data.txnHash
string
On-chain transaction hash. Present when status is "success".
data.txnId
string
Echoes the txId you submitted. Present when status is "success".
data.message
string
Error details. Present when status is "error".

Examples

Once broadcast, poll /v1/status (with chainId and txnHash) to track settlement, especially for cross-chain steps.
Last modified on July 14, 2026