Skip to main content
This is a capital provider’s daily routine for batch orders. Every request carries your API key, and the times are New York time.

Before you start

  • A capital provider with batch orders on, and its id, from GET /v1/batch-orders/capital-providers?network=evm-mainnet: on Ethereum, your stablecoin delegate’s ID. An empty capitalProviders list means your organization has none with batch orders on for the network; Get set up says how to get one.
    Response
  • An operator. An admin, or a key with cp:admin, selects the wallet that executes your orders:
    Without an operator, users cannot place orders with you.
  • On Solana, durable nonce accounts for your operator. Each Solana order uses one, and users cannot place orders while the pool is empty. Batch operations explains how to register them.

1. Post capacity, before 4:30 PM

Set how much of a token you will fill in a batch. posted is the total in whole tokens, with at most 6 decimal places, not an increment: 250000 is 250,000 USTB. token is the token’s address. batchId names the batch by its release date: the batch.batchId that GET /v1/batch-orders/capital-providers returns for the batch now taking orders, or a later date.
It returns the token’s capacity:
Response
You can post for later batches in advance, and change a total until the batch’s 4:30 PM cut-off. A batch’s intakeOpen is about users’ orders only: it is false for a later batch that still takes capacity. Orders reserve capacity as they arrive, so a new total cannot go below what they already reserve.

2. Check what the batch needs

GET /v1/batch-orders/batches/{batchId}/requirements totals the output and protocol fees the batch’s orders need, by capital provider, operator, and token. batchId is the release date, such as 2026-11-06.
Response
Make sure your custody can fund those totals before the release.

3. Retrieve the released orders, at 5:00 PM

GET /v1/batch-orders/payloads returns each released order with its complete signed authorization. Only your organization receives them. The authorization is what the operator executes on-chain, so its assetInAmt and assetOutAmt are in base units: 1000000000 is 1,000 USDC.
Response
On Solana, each payload carries the user-signed transaction with the operator’s signature slot empty.

4. Execute each order

Your operator executes each order on-chain, targeting 5:15 PM and always before the order’s signed deadline. On Solana, the operator adds its signature to the transaction and sends it.

5. Report each outcome, by 5:30 PM

Report every order between the release, at or just after 5:00 PM, and the 5:30 PM close, with a reason:
It answers 201 with the recorded revision:
Response
A report is a claim, not proof. Multiliquid records each order’s outcome from verified on-chain execution, and your latest report counts. An order whose reported success it has not verified is underReview until it does. Reports says what each status does to the order.

When something goes wrong

Users cannot prepare orders while you have no operator (OPERATOR_NOT_SELECTED), or on Solana while your operator has no idle nonce account (NONCE_ACCOUNT_UNAVAILABLE). Errors lists every code.