Skip to main content
After building a swap transaction via POST /api/v1/swap, sign it, submit it to the network, and wait for confirmation.

Full flow

Transaction expiry

Every transaction includes a lastValidBlockHeight. If the transaction is not confirmed by that block height, it expires and can never be included. This is typically around 60 seconds from when the transaction was built. If a transaction expires:
  1. Get a fresh quote (prices may have changed).
  2. Build a new transaction.
  3. Sign and submit again.
Do not resubmit an expired transaction. It will never confirm. Always rebuild from a fresh quote.

Retry strategy

Preflight checks

By default, skipPreflight: false runs a simulation on the RPC node before broadcasting. This catches obvious failures early (wrong signer, insufficient balance, etc.). Set skipPreflight: true only if:
  • You already validated via the /api/v1/swap simulation.
  • You need the lowest possible submission latency.

Confirmation levels

The default confirmTransaction waits for confirmed level, which is appropriate for most swap integrations.
Last modified on August 31, 2026