Skip to main content
POST
Reopens a liquidation the router settled without collecting any proceeds, so collateral that settlement left on the router can move again. It calls the router’s reopenLiquidation, which only the router administrator, the holder of DEFAULT_ADMIN_ROLE on the router, may sign. Afterwards the record reads PENDING and the ordinary legs apply to it again: Withdraw Collateral for Sale, Report Partial Sale and Settle Liquidation.
A settlement closes the router’s record for good, and collateral still on the router at that moment is stranded: it can no longer be withdrawn. Reopening is the only way back, and the router allows it only while the record collected nothing. A record whose settlement routed any cash to the market can never be reopened, and its stranded collateral stays on the router.

When It Applies

Find candidates on List Settled Liquidations, where they read reopenable: true. This API refuses to settle a record while collateral is on the router, so such records come from settlements made outside it, for example directly against the router. Each condition below must hold, and each is checked before any calldata is built. The second column names the refusal when it does not. Reopening touches the router’s record only. The market’s own record keeps its state: still open when the earlier settlement never reached it, settled when it did. Cash a later settlement brings to an already settled market record counts as late proceeds, which make the pool whole on the claim before repaying the insurance fund. The router’s settled count falls by one, so the router is no longer quiet until the record closes again.

Path Parameters

string
required
Liquidation ID on the market’s router.

Body Parameters

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. Also accepted as a query parameter. A value longer than 100 characters is ignored.
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. A value that is not a 0x-prefixed 64-character hex string is ignored.

Response Fields

object
Confirming moves every SETTLED record under this ID on the market back to PENDING. The record keeps the hash of its earlier settlement in settledTxHash.

Error Codes

Confirming with txHash can also return any transaction verification error. A reopen that reverted on-chain is refused there with TX_REVERTED.