Treat every quote as a snapshot-bound instruction set that can expire before the user signs.
Definition
Quotes use the latest pool snapshot available to the service. The response can also encode slippage bounds, route choices, transaction fields, and a TransactionEnvelope or transaction object. Those fields belong to that quote request.
Decision Table
| Need | Action |
|---|
| Display indicative pricing | Quote without sender and refresh on user action |
| Build transaction data | Requote with sender when the user confirms |
| Require Stellar ledger freshness | Set fresh=true on the Stellar quote endpoint |
| Compare route detail | Pass includePaths=true for the request you inspect |
| Retry after route failure | Requote; do not reuse old transaction data |
Worked Example
curl "https://swap.xoxno.com/api/v1/quote?\
from=WEGLD-bd4d79&\
to=USDC-c76f1f&\
amountIn=1000000000000000000&\
slippage=0.01&\
sender=erd1..."
amountOut matches the UI route.amountOutMin reflects the slippage tolerance you showed the user.transaction or txData came from the same quote request.- The user has not changed token, amount, slippage, or sender since the quote.
Edge Cases
| Case | Behavior | Fix |
|---|
| User changes slippage after quote | Encoded transaction data can carry the old minimum output. | Requote. |
| User changes sender | Nonce, gas, source account, or envelope fields can differ. | Requote with the new sender. |
| Pool state changes before signing | Output can differ on-chain or fail slippage checks. | Requote near confirmation. |
| Stellar snapshot is stale | fresh=true can return 409 when drift is above the service threshold. | Retry after the snapshot catches up. |
Do not reuse txData, transaction objects, or TransactionEnvelope values across quote requests.
