Skip to main content
The first three requests change nothing on chain, so they need no API key and no funds. To sign and submit, the wallet needs the input token and ETH for network fees.
1

Find a pair

List the pairs you can offer on Ethereum:
Each pair names the token the user pays, the token they receive, the capital providers that can fill it, and those that take batch orders for it. This one pays USDC for WTGXX, a tokenized money market fund:
Pair
2

Get a quote

Quote 1 USDC into WTGXX for the user’s wallet. Amounts are whole tokens, as decimal strings: 1 USDC is 1.
The user receives amountOut, here 0.9999 WTGXX. fees lists each fee and who pays it, and alternatives lists every other capital provider considered, with the amounts it quoted or the error it rejected the swap with.
Response
If the quote answers NO_QUOTE, no capital provider can fill that amount now, and details.providers says why for each one. Try a smaller amount or another pair.
3

Build the transactions

Send the same swap with the wallet, and how far the price may move in basis points:
The wallet signs approval, then swap. approval lets the capital provider’s delegate take the USDC, and it is null when the wallet has already approved enough. checks show whether the swap would succeed. In this example the wallet holds enough USDC and may receive WTGXX, and only the allowance is missing, so the build simulates the swap after the approval. Each transaction is complete and ready to sign: the API fills in its nonce, gas, maxFeePerGas, and maxPriorityFeePerGas from the chain, and serialized is the unsigned transaction. The approval takes the wallet’s next nonce, 42, and the swap the one after. The transactions are calldata, so the approval’s data encodes 1 USDC in its on-chain base units. The response also carries the build’s own fresh quote under quote, with its amounts, price, fees, and capital provider, left out here.
Response
4

Sign and submit

Sign each transaction’s serialized as returned, without broadcasting it. Don’t change the nonce, gas, or fees: they are set for this wallet and the current fee market. Sign within a few blocks, and build again if the wallet sends another transaction first. Submit them together, the approval first:
Multiliquid broadcasts the approval now and sends the swap once the approval is confirmed. The response lists both submissions in order. Read the swap’s GET /v1/submissions/{submissionId} every 4 seconds until its state is finalized or expired, or failed with finalizedAt set or without inclusion. When approval is null, submit the swap alone.A wallet that can only broadcast, such as a browser wallet or a custody platform, sends the approval itself instead, waits until it is confirmed, then sends the swap as returned, or builds again if more than a few blocks have passed.

Next steps

Swap instantly

The full flow on Ethereum and Solana, from quote to a finalized swap, and what to do when something fails.

Quotes and builds

Every field of a quote and a build.

Submissions

States, polling, and the realized settlement.