POST /v1/submissions relays the transactions of one swap build that the user signed, or on its own the approval that a batch order or redemption preparation returns. Multiliquid decodes them, checks that they are Multiliquid transactions, simulates and broadcasts the first, sends the second once the first is confirmed, and tracks each until it is final. Multiliquid never pays a fee: each signed transaction pays its own.
Submitting
The body is{"network": "...", "signedTransactions": [...]}, with the transactions in signing order: one transaction, or a build’s two, its approval then its swap on EVM, or its accountCreation then its swap on Solana. The approval of a batch order or a redemption preparation is submitted alone. Send a signed EVM transaction as 0x-prefixed EIP-2718 hex, and a signed Solana transaction as base64 wire bytes.
An EVM transaction that a build or preparation returns is complete, with its nonce, gas, and fees filled in: the wallet signs it as returned. Two EVM transactions come from one wallet with consecutive nonces, as a build’s approval and swap do. If the wallet sent another transaction after the build, its nonce is used, and submission answers 409 with NONCE_ALREADY_USED: build again and sign the new transactions.
signedTransactions that holds no transaction or more than two, or a network the API does not know, answers 422 with code INVALID_BODY and details.field. A network that the API does not serve answers 503 with code NETWORK_NOT_ACTIVE and details.network. Neither reads a transaction. Otherwise Multiliquid checks every transaction before it sends any, in this order, and rejects the request with the first failing code, with 422 unless noted. For INVALID_TRANSACTION and UNSUPPORTED_TRANSACTION, details.field names the transaction, such as signedTransactions[1]. A rejected request stores nothing.
- Decoding and signatures (
INVALID_TRANSACTION). EVM accepts legacy (EIP-155), EIP-2930, and EIP-1559 transactions for the network’s chain, of at most 8,192 bytes, and no contract creation. Solana accepts legacy and version 0 transactions, including version 0 transactions with address lookup tables, of at most 1,232 bytes, with every required signature present and valid; version 1 transactions are not accepted. Two EVM transactions must have one sender and consecutive nonces, and two Solana transactions one fee payer and different signatures. - Multiliquid transactions (
UNSUPPORTED_TRANSACTION). On EVM, a call with no ETH value to the network’s swap contract or a listed stablecoin delegate, or an ERC-20approveof a listed token whose spender is one of them. On Solana, a transaction with at least one swap or Treasury program instruction whose other instructions are compute-budget, associated-token-account, SPL Token, or Token-2022 instructions, or a build’saccountCreation. A Solana durable-nonce transaction, which starts with a System Program instruction, is rejected here. Two transactions must be a build’sapprovaloraccountCreationfollowed by itsswap. - Nonce or blockhash. On EVM, a nonce the sender already used is a
409with codeNONCE_ALREADY_USED. On Solana, a blockhash the network no longer accepts isINVALID_TRANSACTION, and the transactions are built again. - Simulation (
SIMULATION_FAILED) of the first transaction at the latest block or slot. The message names the decoded revert or program error. - Broadcast of the first transaction. A node that refuses it rejects the request with
TRANSACTION_REJECTED. A broadcast that does not reach the node is a503with codeSERVICE_UNAVAILABLE.
queued. Once the first is confirmed, Multiliquid simulates the second and broadcasts it, and it becomes pending. If the first fails or expires, the second becomes failed without being sent, with error.code PREVIOUS_TRANSACTION_FAILED. If it fails in simulation, or the node refuses it, when its turn comes, it becomes failed with SIMULATION_FAILED or TRANSACTION_REJECTED. If by then another transaction used its nonce (EVM) or its blockhash expired (Solana), it becomes expired.
The response is {"submissions": [...]}, a submission for each transaction in the request’s order, each with replayed. It is 202 when any submission is new, with replayed: false on each new one. Here the approval is broadcast and the swap waits behind it:
Response
replayed: true, and a request whose transactions were all submitted before returns 200. A transaction submitted alone and then again with the one after it is a replay, and the later one queues behind it. A transaction that already landed, as when a broadcast’s response was lost, is accepted without being simulated or broadcast again.
A submission
GET /v1/submissions/{submissionId} returns one submission to any caller. submissionId is a UUID; any other value answers 400, and an unknown one 404. Once the swap above is final, it reads:
Response
The four timestamps are RFC 3339 in UTC with whole seconds, such as
2026-11-06T17:19:04Z. A value that a submission does not have yet, such as the inclusion of a pending one, is present and null.
States
Confirmation
confirmed means the transaction is in the chain, not that it is final:
- On Ethereum, a submission is
confirmedas soon as its receipt is in a block, with no further blocks after it. It becomesfinalizedwhen that block is finalized, about 13 minutes later. - On Solana, it is
confirmedat theconfirmedcommitment, when a supermajority of validators has voted on its slot. It becomesfinalizedat thefinalizedcommitment, about 13 seconds later.
confirmed. If a reorganization then removes the first, the second can fail.
A chain reorganization on EVM, or a dropped fork on Solana, that removes an inclusion returns a confirmed or failed submission to pending and clears its inclusion, error, confirmedAt, finalizedAt, and settlement. Multiliquid tracks it again, and it can be included in another block or slot. Act on confirmed only where a reversal is acceptable, and on finalized otherwise.
Errors
Afailed submission’s error says why:
A transaction that was never sent has no
name.
You don’t need to rebroadcast. While a submission is pending, Multiliquid rebroadcasts an EVM transaction at most once a minute until its nonce is used, and a Solana transaction every two seconds until its blockhash expires.
Polling
Multiliquid observes submissions at a fixed pace, so polling faster returns the same answer and only spends the rate allowance:
Stop polling at
finalized, at expired, and at failed once finalizedAt is set, or at once when it has no inclusion.
Settlement
Aconfirmed or finalized swap carries settlement, the realized swap decoded from its own on-chain event when Multiliquid records the inclusion. It is the same object a batch order’s settlement is: transactionId, blockNumber (a decimal string, the slot on Solana), settledAt, and legs. A submission’s settledAt is null, because Multiliquid does not record the block’s time; confirmedAt is when it observed the inclusion. The one leg, legIndex 0, has inputToken and outputToken as token objects, the realized amountIn and amountOut in whole tokens, and fees, each {type, amount, token, paidBy} with amount in whole tokens of token:
- On EVM, the swap contract’s event for the swap’s single leg, with the issuer, spread, and capital provider fees in the capital provider’s stablecoin.
- On Solana, the swap program’s event, with one
protocolfee in the global fee token: the issuer fee and the spread, which the program transfers together. ItspaidByiscapitalProvider, which describes the issuer share; the spread share and the pair fee are already reflected in the amounts.
kind is swap only when its transaction swaps exactly once, so its inclusion is one settlement. A confirmed or finalized swap has a null settlement only when:
- Multiliquid could not decode its on-chain evidence;
- on EVM, Multiliquid could not read the tokens the swap contract registered for its assets within about half an hour of confirmation; or
- it was relayed or finalized before Multiliquid recorded settlements.
null symbol, name, and issuer, and on Solana a null kind. A leg’s amountIn or amountOut is null only when its token, and so its decimals, cannot be resolved. The interactive reference gives the exact fees fields of each runtime.
Organization submissions
A submission made with a credential belongs to the credential’s organization. A submission made without one belongs to the organization of the first credential that submits the same signed transaction again, and a submission keeps the first organization it belongs to.GET /v1/submissions?network= lists the organization’s submissions on one network, newest first, in the same form as a single submission. It requires a credential and answers 401 without one, and 403 with code INSUFFICIENT_SCOPE for an API key without the read scope. The list reads stored submissions only, so it answers for every network key, whether or not the API currently serves the network.
submissions and nextCursor, which is null on the last page. A submission that belongs to no organization is never listed.
A limit outside 1 to 100, an invalid user, an unknown network, or a cursor that is malformed or was issued for another network, other filters, or another organization answers 400 with code INVALID_REQUEST, details.field naming the parameter, and details.location query. An unknown query parameter is also a 400.
Limits
The body is limited to 40 KiB, with one or two signed transactions, each of at most 8,192 bytes on EVM or 1,232 bytes (1,644 base64 characters) on Solana.POST /v1/submissions is in the anonymous write allowance, and both GET routes in the read allowance, of Rate limits.
Related
Quotes and builds
The transactions a build returns for the wallet to sign.
Retries and idempotency
Safe retries after a timeout or a
503.