Execute - DZap

curl -X POST https://api.dzap.io/v1/gasless/executeTx \
  -H "Content-Type: application/json" \
  -d '{
    "chainId": 42161,
    "txId": "0xabc...",
    "permit": {
      "permitData": [{ "token": "0xaf88...", "amount": "1000000", "permit": "0x..." }],
      "gaslessIntentSignature": "0x...",
      "gaslessIntentDeadline": "1714200000",
      "gaslessIntentNonce": "1"
    }
  }'

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

// Standard flow: sign the build response, then broadcast
const result = await dzap.broadcastTradeTx({
  txId: '0xabc...',
  chainId: 42161,
  txData: '0x02f8b0...', // signed raw transaction
});

// Gasless flow (executeTx has no standalone SDK method - it's called
// internally by tradeGasless() as part of the sign+submit flow)
const gaslessResult = await dzap.tradeGasless({ request, signer });

{
  "status": "success",
  "txnHash": "0xdef456..."
}

{
  "status": "success",
  "txnHash": "0xdef456..."
}

POST

gasless

executeTx

curl -X POST https://api.dzap.io/v1/gasless/executeTx \
  -H "Content-Type: application/json" \
  -d '{
    "chainId": 42161,
    "txId": "0xabc...",
    "permit": {
      "permitData": [{ "token": "0xaf88...", "amount": "1000000", "permit": "0x..." }],
      "gaslessIntentSignature": "0x...",
      "gaslessIntentDeadline": "1714200000",
      "gaslessIntentNonce": "1"
    }
  }'

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

// Standard flow: sign the build response, then broadcast
const result = await dzap.broadcastTradeTx({
  txId: '0xabc...',
  chainId: 42161,
  txData: '0x02f8b0...', // signed raw transaction
});

// Gasless flow (executeTx has no standalone SDK method - it's called
// internally by tradeGasless() as part of the sign+submit flow)
const gaslessResult = await dzap.tradeGasless({ request, signer });

{
  "status": "success",
  "txnHash": "0xdef456..."
}

{
  "status": "success",
  "txnHash": "0xdef456..."
}

There are two ways to finalize a built transaction, depending on the gasless flag you passed to /v1/buildTx:

Gasless (gasless: true) - the user signs the typed-data payload from the build response; you submit that signature to /v1/gasless/executeTx and DZap’s relay executes it.
Standard (gasless: false) - the user signs the raw transaction from the build response; you submit the signed transaction to /v1/broadcast.

Execute a gasless intent

POST https://api.dzap.io/v1/gasless/executeTx

Body

chainId

integer

required

Chain ID the intent targets.

txId

string

required

The txId from the gasless /v1/buildTx response.

permit

object

required

Either an EIP-2612 permit payload or a batch-permit payload, depending on what your wallet signed.

Show permit (EIP-2612)

permitData

object[]

Array of { token, amount, permit } - one per token requiring a permit signature.

gaslessIntentSignature

string

Signature over the gasless intent typed data.

gaslessIntentDeadline

string

Deadline for the signed intent.

gaslessIntentNonce

string

Nonce for the signed intent.

Show permit (batch)

batchPermitData

string

Encoded batch-permit payload.

Response

status

string

Transaction status (success, mining, error, etc.).

txnHash

string

On-chain transaction hash.

Broadcast a signed transaction

POST https://api.dzap.io/v1/broadcast

Body

txId

string

required

The txId from the non-gasless /v1/buildTx response.

chainId

integer

required

Chain ID to broadcast on.

txData

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

status

string

"success" or an error status.

txnHash

string

On-chain transaction hash. Present when status is "success".

message

string

Error details. Present when status is not "success".

Examples

curl -X POST https://api.dzap.io/v1/gasless/executeTx \
  -H "Content-Type: application/json" \
  -d '{
    "chainId": 42161,
    "txId": "0xabc...",
    "permit": {
      "permitData": [{ "token": "0xaf88...", "amount": "1000000", "permit": "0x..." }],
      "gaslessIntentSignature": "0x...",
      "gaslessIntentDeadline": "1714200000",
      "gaslessIntentNonce": "1"
    }
  }'

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

// Standard flow: sign the build response, then broadcast
const result = await dzap.broadcastTradeTx({
  txId: '0xabc...',
  chainId: 42161,
  txData: '0x02f8b0...', // signed raw transaction
});

// Gasless flow (executeTx has no standalone SDK method - it's called
// internally by tradeGasless() as part of the sign+submit flow)
const gaslessResult = await dzap.tradeGasless({ request, signer });

{
  "status": "success",
  "txnHash": "0xdef456..."
}

{
  "status": "success",
  "txnHash": "0xdef456..."
}

Once submitted, poll /v1/status with the resulting txnHash and chainId to track settlement - especially for cross-chain bridges.

Last modified on July 14, 2026

Build Tx Status

​Execute a gasless intent

​Body

​Response

​Broadcast a signed transaction

​Body

​Response

​Examples

Execute a gasless intent

Body

Response

Broadcast a signed transaction

Body

Response

Examples