Skip to main content
POST
Records any mined transaction of the extension flow: a proposal, a confirmation, an applied batch page, a cancellation, or the switch itself. The API verifies the receipt against the market, reads the extension events it carries, and brings each proposal it touched up to date from the chain. The market assigns a proposal its ID only when the proposal mines, so confirming the proposing transaction here is how to learn it. List Extensions shows it too from then on.
An applied batch page can mine without extending anything. When every loan in the page was outside the batch, closed, or already at or past the proposed date, the response carries noOp: true and outcome: "NO_LOAN_EXTENDED". The transaction still cost gas, and no maturity moved.

Path Parameters

string
required
Market ID.

Body Parameters

string
required
Hash of the mined transaction. It must call proposeExtension, confirmExtension, applyExtension, cancelExtension or setAllowExtension on this market.
Confirming the same hash again is safe. The records converge on the same state, and an applied page is counted once.

Response Fields

object

Error Codes

The transaction checks answer with the standard transaction verification errors: TX_NOT_FOUND, TX_REVERTED, TX_WRONG_TARGET and TX_WRONG_FUNCTION.