Skip to main content
POST
Transfers seized collateral from the liquidation router to the market’s sale recipient, so it can be sold off-platform. This is step one of the manual settlement workflow. External securities have no on-platform venue, so nothing sells automatically. The operator withdraws the collateral, arranges the sale through their own channel, and reports the proceeds back.
The destination is not yours to choose. The lender of record fixed a sale recipient when it took the role, and the router has no setter for it. Sending seized collateral anywhere else is impossible; rotating the destination means deploying a new market.

Path Parameters

string
required
Liquidation ID on the market’s router, from Get Pending Liquidations or from the Liquidate Loan response.

Body Parameters

string
required
Collateral to withdraw, as a decimal string in collateral token units. Must be greater than zero and no more than collateralRemaining.
string
Only meaningful on markets that predate the fixed sale recipient, where it is required and names the destination. On current markets the destination is already fixed: supply nothing, or supply exactly the market’s saleRecipient. Any other address is refused with RECIPIENT_FIXED.
string
Names the market whose liquidation you mean. Every market runs its own liquidation router and IDs restart at 1 on each of them, so the same liquidationId can exist on several markets in one instance. Supply this when it does, otherwise the call is refused with AMBIGUOUS_LIQUIDATION_ID and the response lists the candidates.
string
Hash of the transaction you broadcast for this operation. Send it to confirm the transaction and record the result. Omit it to receive the calldata.
The signing wallet must hold OPERATOR_ROLE on the market’s liquidation router. If it does not, the calldata is not returned: the response carries ROUTER_OPERATOR_ROLE_MISSING along with the calldata that grants the role.

Response Fields

object
Withdrawal is repeatable. Take the collateral out in tranches as sales are arranged. Each call reduces collateralRemaining on the router. The liquidation’s status stays PENDING throughout, so track progress through collateralRemaining rather than status.
If the liquidation ID exists on-chain but has no Trusset record, the endpoint adopts it automatically by scanning your instance’s routers. Liquidations triggered outside this API are therefore still settleable through it.

Error Codes