Integration guide - XOXNO Docs

Choose the execution model first, then keep pricing, preparation, signing, and confirmation distinct.

TypeScript SDK

Quote, verify the route, and build the swap transaction in a few calls.

Runnable example

A complete HTTP-only lifecycle: quote, sign, submit, and confirm.

Pick your integration

Wallets and dapps
Bots
Lending and contracts
Liquidity (LP)

Load token metadata and deployment configuration; keep canonical IDs and network identity.
Quote without a sender for display. Cancel or ignore responses from superseded user input.
At confirmation, requote with explicit slippage, the selected referral, and sender. Verify the net amounts and fee disclosure.
Inspect transaction.envelopeXdr. When transaction.simulated is true, the server already populated the account sequence and prepared resources, fees, and authorizations. Otherwise populate the sequence and prepare Soroban resources first.
Sign through the wallet, submit, and poll for a final result. Show success only after successful execution.

A quote is not proof of balances, authorization, or final settlement. Decode and verify the actual envelope before asking the wallet to sign.

Use atomic amounts for comparisons and accounting.
Bound concurrent requests, back off, and discard obsolete quotes.
Compare net output after swap fees. Count network fees separately when judging profitability.
Reduced path counts can improve reliability but lower output. Check degraded and the actual result.
A tighter freshness gate (fresh=true) detects an old snapshot but adds an RPC round trip.

Coordinate account sequences across concurrent submissions. After an uncertain submission, query its status before sending another swap. Retrying blindly can execute the economic action twice.

Consume routeXdr through the supported SDK or contract interface. Keep the payload opaque and bind it to the intended request. Simulate the complete outer transaction, including its authorizations and the aggregator call.

A wallet TransactionEnvelope cannot stand in for the strategy payload.
A multi-transaction wallet plan is not one atomic lending operation.
Use an independently supplied routeXdr for atomic composition only after simulating the complete outer transaction. If it is absent, atomic composition is unavailable.

Token metadata marks pool shares with lp=true. Explain the pool and its constituents before execution; LP output is a position, not a single underlying token.Handle both transaction and transactions. For an ordered plan, confirm one transaction, refresh the account and balances, then prepare and sign the next. Plan for partial completion: keep the intermediate asset and offer a fresh quote for the remaining action.

Confirmation checklist

Network, router, source account, and canonical token IDs match the intended deployment and wallet.

Atomic input, net output, fee disclosure, and minimum output match what the user confirmed.

The payload or envelope comes from the current quote, with explicit slippage.

Simulation status is read from the transaction object, and the complete outer transaction is prepared for composition.

Submission is tracked through final execution, including failures and uncertain responses.

Quote phases · Execution models · Error recovery

TypeScript SDK

Runnable example

​Pick your integration

​Confirmation checklist

Pick your integration

Confirmation checklist