Skip to main content
GET
Returns the readiness of the liquidation path for a market: every gate liquidate passes through, the onward delivery of seized collateral to the sale recipient, and aggregate liquidation counters. Call this before relying on liquidation. A market can accept loans while its liquidation path is incomplete, which leaves bad debt with no remedy. Realization is two hops with two different signers, so readiness carries two aggregates. seizureConfigured covers everything up to and including moving collateral to the router. isConfigured covers that and one thing more: the collateral must also be able to leave the router for the sale recipient.

Path Parameters

string
required
Market ID.

Query Parameters

string
Wallet to evaluate the role and signer checks against. Omit to use your instance’s registered wallet. Anything that is not a valid address is ignored.

Response Fields

object
routerTokenEligible is reported as true when the collateral token exposes no identity registry and no contract allow-list, because eligibility cannot be evaluated without one. That is an unknown, not a pass. Confirm the router’s compliance status out of band for such markets.
operatorRoleReady and liquidatorRoleReady are evaluated against signerAddress, or against your instance’s registered wallet when it is omitted. If the market’s lender of record named a different liquidationOperator, settlement runs through that wallet rather than this API and the flag reads false by design. Pass signerAddress to ask about that wallet instead.

Transfer Restriction Codes

collateralTransferCode and saleDeliveryCode are the collateral token’s own ERC-3643 restriction codes. 0 means the transfer is permitted, and null means the check did not run.

Error Codes