> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dzap.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Broadcast Transaction

> Submit a signed transaction for a standard (non-gasless) trade to be broadcast on-chain.

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](/api/trade/execute) instead.

## Body

<ParamField body="txId" type="string" required>The `txId` from the non-gasless `/v1/buildTx` response.</ParamField>

<ParamField body="chainId" type="integer" required>Chain ID to broadcast on.</ParamField>

<ParamField body="txData" type="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.
</ParamField>

## Response

<ResponseField name="status" type="string">`"success"` or an error status.</ResponseField>

<ResponseField name="txnHash" type="string">On-chain transaction hash. Present when `status` is `"success"`.</ResponseField>

<ResponseField name="message" type="string">Error details. Present when `status` is not `"success"`.</ResponseField>

<RequestExample>
  ```bash curl theme={null}
  curl -X POST https://api.dzap.io/v1/broadcast \
    -H "Content-Type: application/json" \
    -d '{
      "txId": "0xabc...",
      "chainId": 42161,
      "txData": "0x02f8b0..."
    }'
  ```

  ```ts SDK theme={null}
  const result = await dzap.broadcastTradeTx({
    txId: '0xabc...',
    chainId: 42161,
    txData: '0x02f8b0...', // signed raw transaction
  });
  ```
</RequestExample>

<ResponseExample>
  ```json 200 theme={null}
  {
    "status": "success",
    "txnHash": "0xdef456..."
  }
  ```
</ResponseExample>

<Note>
  Once submitted, poll [`/v1/status`](/api/trade/status) with the resulting `txnHash` and `chainId` to track settlement - especially for cross-chain bridges.
</Note>