Quickstart - XOXNO Docs

Start with token discovery, then request indicative pricing. Use the API tab for the generated request and response reference.

1. Discover the deployment and tokens

curl --fail-with-body https://stellar-swap.xoxno.com/api/v1/config
curl --fail-with-body https://stellar-swap.xoxno.com/api/v1/tokens

Choose two token id values from the response. They must be canonical C-strkeys, not symbols. Read the input token’s decimals and convert the amount into an integer string.

2. Request pricing

Set the shell variables to the selected contract IDs and raw input amount:

: "${TOKEN_IN:?Set TOKEN_IN to the input C-strkey}"
: "${TOKEN_OUT:?Set TOKEN_OUT to the output C-strkey}"
: "${AMOUNT_IN:?Set AMOUNT_IN to the atomic integer amount}"
curl --fail-with-body --get https://stellar-swap.xoxno.com/api/v1/quote \
  --data-urlencode "from=$TOKEN_IN" \
  --data-urlencode "to=$TOKEN_OUT" \
  --data-urlencode "amount_in=$AMOUNT_IN"

Inspect amountOut, the expected output after swap fees. Use atomic strings for calculations. Human-readable numeric fields are for display.

3. Requote for execution

Ask the user to choose slippage and connect their wallet. Add the sender and explicit tolerance to a fresh quote:

: "${SENDER:?Set SENDER to the wallet G-strkey}"
: "${SLIPPAGE:?Set SLIPPAGE to the accepted decimal tolerance}"
curl --fail-with-body --get https://stellar-swap.xoxno.com/api/v1/quote \
  --data-urlencode "from=$TOKEN_IN" \
  --data-urlencode "to=$TOKEN_OUT" \
  --data-urlencode "amount_in=$AMOUNT_IN" \
  --data-urlencode "sender=$SENDER" \
  --data-urlencode "slippage=$SLIPPAGE" \
  --data-urlencode "fresh=true"

For example, 0.01 means 1% slippage. A live freshness check can reject a stale snapshot; retry after it catches up.

4. Inspect, sign, and confirm

For a single transaction, inspect transaction.envelopeXdr, the network, router, input, and minimum output. When transaction.simulated is true, the server has populated the source account’s current sequence + 1 and prepared Soroban resources, fees, and authorizations: sign through your wallet and submit through Stellar RPC. When it is false, populate the sequence and prepare resources first. Wait for successful execution. Request a new quote if another transaction uses the same source account before submission. If the response contains transactions[], follow the ordered plan procedure. If you are composing with lending, use the opaque route payload and simulate the outer transaction instead. Integration checklist · Quote phases · Troubleshooting

​1. Discover the deployment and tokens

​2. Request pricing

​3. Requote for execution

​4. Inspect, sign, and confirm

1. Discover the deployment and tokens

2. Request pricing

3. Requote for execution

4. Inspect, sign, and confirm