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, or to the auction venue when Dutch auctions are on. isConfigured covers that and more: the router’s operator must hold its role, and the collateral must be able to leave the router for the sale recipient.

Path Parameters

string
required
The market’s record ID, as id on List Markets, not its contract address. See Market IDs. At most 100 characters.

Query Parameters

string
Wallet to evaluate the liquidator role against. Omit to use your instance’s primary verified wallet. When sent, atomic.signer also reports its router roles. 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. routerTokenRequirement reads none_required in that case. Confirm the router’s compliance status out of band for such markets.
The two role flags answer for different wallets. liquidatorRoleReady answers for signerAddress, or your instance’s primary verified wallet when it is omitted, and also counts a connected liquidation bot. operatorRoleReady answers for the liquidation operator the market records, and falls back to that same wallet only when the market records none. The settlement endpoints of this API, apart from Sell Pending Liquidation, check OPERATOR_ROLE against your instance’s primary verified wallet, so a market whose operator is a different wallet settles outside this API.
The examples below shorten atomic or leave it out.

Transfer Restriction Codes

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

Error Codes