Skip to main content
POST
Transfers seized collateral from the liquidation router to a recipient you nominate, 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 recipient must satisfy the collateral token’s compliance rules. ERC-3643 transfers to an unverified or non-allowlisted address revert, surfacing as WITHDRAW_PREFLIGHT_FAILED. Verify the recipient on the token’s identity registry before calling.

Path Parameters

string
required
Global router liquidation ID from Get Pending Liquidations or from the Liquidate Loan response.

Body Parameters

string
required
Wallet or custodian address receiving the collateral. Must be a 0x-prefixed 40-character hex address.
string
required
Collateral to withdraw, as a decimal string in collateral token units. Must be greater than zero and no more than collateralRemaining.
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.

Errors