Cross-Chain Swap API

How cross-chain routing works

Cross-chain execution moves value between networks, often through one or more liquidity and messaging providers. Routes differ by token coverage, fees, destination gas, settlement time, custody assumptions and fallback behavior.

A quoted route is an estimate, not guaranteed final settlement. The relevant contracts and bridge providers determine actual execution and eventual destination receipt.

Typical integration flow

Applications should fetch supported chain and token configuration at runtime, construct a quote request with precise amounts, inspect route fees and expected outputs, and build the relevant transaction once the user chooses a route.

• Read up-to-date supported networks and token decimals.
• Fetch and compare available routes based on net output and other constraints.
• Review token approvals and clearly identify the wallet's required signatures.
• Submit with user authorization and monitor route/transaction status.
• Surface failures, refund conditions and destination-state uncertainty.

What to validate before launch

Integrators should use testnets or fork-based tests where supported, and exercise provider timeouts, bridge delays, gas shortfalls, stale quotes and token approval failures. Rate-limit external API calls and protect high-fan-out quote endpoints.

For precise authentication, request schemas and response fields, the API documentation takes precedence over this marketing explanation.

When to consider intent execution

If users want a destination outcome rather than manual orchestration of every transaction leg, compare direct routing with DZap's intent-based Fuse model. Execution and signature semantics differ, so choose the appropriate integration for the custody and recovery guarantees your app requires.