New
- Swap API. Discover networks and pairs, then quote, build, and relay swaps on Ethereum and Solana. Swap API
- Redemption preparation.
POST /v1/redemptions/preparereturns the redemption to send back, the typed data to sign, the $TSY approval it needs, and checks that show whether intake would accept it. Redeem at size - Organization keys and scopes. An admin can create keys that belong to the organization, each with the scopes it needs:
read,trade,cp:operate, orcp:admin. Authentication - Testnets.
evm-sepoliaandsvm-devnetrun on the production host. Testnets - Solana asset decimals. Solana deployment info gives each asset’s
decimals, as Ethereum deployment info does. Deployment info - Decode a transaction.
POST /v1/swap/decodesays what a transaction does, with its function or instructions, labels for the addresses Multiliquid lists, and a summary to show the user. Decode - Your organization.
GET /v1/organizationreturns the organization a credential acts for, itsidandname, for any API key of any scope or an account session with a selected organization. An account session that selects none gets403with the new codeORGANIZATION_NOT_SELECTEDon every route it is sent to, public routes included. Delegates - Batch order capacity check. Batch order preparation returns
checks.capacity, which compares what the order would reserve with the capacity the capital provider has left, on Ethereum and Solana. Checks - Delegate administration.
GET /v1/organizations/{organizationId}/delegates/{delegateId}/admin/statereads a stablecoin delegate’s on-chain configuration, with optional whitelist, blacklist, and admin checks, for a key withread.POST /v1/organizations/{organizationId}/delegates/{delegateId}/admin/preparereturns the unsigned transaction for one admin action, such as whitelisting an RWA, setting a rate or custody address, or pausing, with checks of whether it would succeed, for a key withcp:admin. Your capital provider admin wallet signs and sends it. Administer your delegate TOKEN_ACCOUNT_MISSING. A Solana batch order whose user lacks a token account for the pair answers this code, with the mint, the account, and its token program indetails. Batch orders
Changed
- Ethereum transactions are ready to sign. Every unsigned EVM transaction the API returns, a build’s
approvalandswap, a batch order’s or redemption’sapproval, and a delegate admin transaction, carries the sender’snonce,gas,maxFeePerGas, andmaxPriorityFeePerGas, read from the chain, andserialized, the unsigned EIP-1559 bytes to sign. Sign it as returned, without setting a nonce or fees. An approval and a swap take consecutive nonces, and a swap that needs an approval is simulated after it, so it has its owngas.checks.simulationreportsapprovalRequiredonly when the swap can be simulated only after its approval lands, and the newapprovalRevertswhen the approval itself would revert, with the approval’s revert aserror.gasandserializedarenullfor a transaction that cannot succeed now. A transaction whose nonce was used since the build gets409NONCE_ALREADY_USEDfromPOST /v1/submissions: build again.POST /v1/swap/decoderejects aserializedthat does not match its transaction’s fields. Transactions on EVM - Amounts are whole tokens. Every token amount the API takes or returns is in whole tokens, as a decimal string such as
"1500.25", in place of base units: quotes, builds, fees, checks, batch orders and capacity, redemptions, settlements,/v1/transactions, decoded effects, and errordetails. A request’s amount has at most 6 decimal places and no more than the token’s decimals, and is never a JSON number; a response’s is exact, andnullwhere the token’s decimals are unknown. This breaks a client that sends base units:"1000000"USDC now means a million USDC, and a value with too many decimal places is rejected. What the user signs keeps base units: typed data, prepared batch order and redemption bodies, and transaction calldata,value, and gas. A submission’sinclusion.feeis whole ETH or SOL, each redemption check and shortfall error names itstoken, and percentages are whole basis points named…Bps. Amounts - One network vocabulary. Every route takes
evm-mainnet,evm-sepolia,svm-mainnet, orsvm-devnet. Network keys - Errors say what to do. Every error carries a
code, arequestId, anddetailswhere there is more to say. Errors - One set of names. Fields are
camelCase, and every resource you poll reports astate. Conventions - Batch orders move to
/v1/batch-orders, with one flow on both chains: prepare, sign, and submit, with the Ethereum approval as a transaction to sign, and cancellations prepared and signed the same way. Reads look like a swap, with the statesaccepted,processing,completed,failed,canceled, andunderReview. A batch’s ID isbatchId, and pairs list the capital providers that take batch orders inbatchCapitalProviders. The capital provider routes move under/v1/batch-orders/capital-providers. Place a batch order - Redemptions are prepare, sign, and submit:
POST /v1/redemptionstakes{redemption, signature}. Reads name amounts as a swap does,amountInandamountOut, and report astate, astatusDetail, and asettlement.GET /v1/redemptions/configandGET /v1/redemptions/eligibilityare removed, because preparation returns what they did. Redeem at size - A build names its transactions.
POST /v1/swap/build, in place ofPOST /v1/swap/transaction, returnsapprovalon Ethereum oraccountCreationon Solana, eachnullwhen not needed, thenswap, in place ofsteps. Eachdescriptiongives its amounts, such asSwap 1 USDC for at least 0.9949005 WTGXX. Build response - Quotes give what the user confirms. A quote no longer carries
routeorobservedAt, and eachnaventry is itstoken,value, andcurrency. A build’squoteis the amounts, price, fees, and capital provider. Quote response - One submission request per build.
POST /v1/submissionstakes a build’s transactions together, assignedTransactions, and sends the swap once the approval or account creation before it is confirmed. A transaction waiting its turn isqueued, and a failed submission’serrorcarries acode. Submissions GET /v1/swap/tokensis removed.GET /v1/swap/pairslists every token. Discovery- Rate limits rise to 300 requests a minute for each group of anonymous routes, and 600 a minute for requests with a credential. Rate limits
- Quotes use only the listed capital providers. A quote or build considers only the capital providers whose delegates whitelist the pair, the ones
GET /v1/swap/pairslists, so a $TSY-to-USDC quote is filled by the Treasury capital provider alone, and answersNO_QUOTEabove what Treasury custody can pay out. A namedcapitalProviderthat the pair does not list answersUNSUPPORTED_PAIR. Discovery - $TSY quotes follow Treasury credits. With
user, $TSY in above the user’s credits, none included, is rejected withInsufficientCredits. Withoutuser, a $TSY quote isindicative, priced as a wallet with no accrued yield would be. $TSY that cannot be priced now is rejected withCreditsUnavailable, and any Ethereum quote that rounds to zero withZeroAmount. Quote - $TSY mint eligibility. A build whose $TSY output the Treasury capital provider mints checks the receiver against the $TSY allowlist, and reports
allowlistedornotAllowlisted. Eligibility - Approvals name their spender. An approval’s
descriptionnames the delegate as decode labels it, such asApprove 1 USDC to the USDC delegate of capital provider Uniform Labs. Build response - Quotes and builds are not cached. Both answer with
Cache-Control: no-store. Quote - Redemption preparation reports failing checks.
POST /v1/redemptions/prepareanswers200when the depositor’s Treasury credits fall short, none included, withchecks.creditsfailing, and prices the full amount at the depositor’s own rate. An amount too small to redeem isINVALID_BODY, and a quote that reverts isNO_QUOTEwithdetails.providers.checks.liquidity.availableandINSUFFICIENT_LIQUIDITY’sdetails.availableare the most USDC Multiliquid can pay out now, whatever the redemption’s size, andchecks.liquidity.sufficientis intake’s decision. Prepare and sign - Redemption intake order. Intake checks the form of every field, the signature’s included, before the operator, and
UNSUPPORTED_ROUTEnames its field. Lifecycle - Errors carry more
details. Batch order preparation’sNO_QUOTEnames the capital provider and the decoded error, as a swap quote’s does,UNSUPPORTED_FIELDgives thefieldandnetwork, and the info routes name a rejectedruntimeorchainindetails.field. Errors - Stricter requests, consistent addresses. Every route rejects an unknown query parameter with
INVALID_REQUEST, and points a credential sent in the query string to theAuthorizationheader. AnINVALID_REQUESTorINVALID_BODYerror givesdetails.fieldwhen one value is at fault, anddetails.locationwhen its place is known. A rejected network name is followed by its canonical key, such asunsupported network `mainnet` (evm-mainnet).GET /v1/infoandGET /v1/volumereturn addresses in lowercase hex, as every other route does. Conventions - List cursors. A cursor continues only the listing it was issued for: the same route, network, and filters, and for a private list the same organization. A cursor issued before this release is rejected; start the list again. Conventions
- The OpenAPI document’s version. Its
info.versionis the release the API runs. Introduction
Deprecated
- The flat redemption body.
POST /v1/redemptionsstill accepts the earlier flat body, which SDK 0.5.x sends, but it is deprecated. Send{redemption, signature}. Redeem at size - The
requestIdandstatusredemption filters.GET /v1/redemptionsstill accepts them, because SDK 0.5.x sends them, but they are deprecated. Filter byredemptionIdandstate. Listing redemptions