After executing a trade, you need to monitor its progress, especially for cross-chain transactions that may take several minutes to complete.The DZap SDK provides status tracking for all trade types, from simple swaps to complex cross-chain bridges.
Rate Limits: Our API and SDK have rate limits in place to ensure fair usage.
If you need increased rate limits for your application, please reach out to our
team on Telegram.
Basic Status Tracking
Here’s how to check the status of a completed trade:Status Request Parameters
ThegetTradeTxnStatus function accepts either a txHash or a txId, always paired with chainId:
Status Response Structure
The status response follows theTradeStatusResponse type — a single flat object (not keyed by pair), with a transactions array covering each leg of the trade:
Polling for Trade Completion
For cross-chain trades, poll until the transaction reaches a terminal state:Checking Multiple Transactions
UsegetTradeMultiTxnStatus to check several transactions in one call. It accepts comma-separated txHashes/txIds aligned positionally to comma-separated chainIds, and returns an array of TradeStatusResponse:
Best Practices
- Implement proper polling intervals - Don’t poll too frequently to avoid rate limits (recommended: 10s+)
- Handle all status types - Prepare for successful, failed, and pending states
- Set a timeout - Cross-chain trades can take minutes, but shouldn’t hang indefinitely
Cross-chain transactions can take anywhere from a few minutes to an hour
depending on the bridge used and network congestion.