Skip to main content
POST
Builds the setAllowExtension transaction, the master switch over maturity extensions. Requires DEFAULT_ADMIN_ROLE on the market, held by the admin the lender of record named at adoption. The market’s creator never holds that role, so extensions exist on a market only when its lender of record chooses to offer them. An extension moves a maturity the borrower signed, and it needs no signature from the borrower. Switch the flow on only where the lender of record’s terms of use provide for extensions. With the switch off, no extension can be proposed, confirmed or applied, while an open proposal can still be cancelled. Switching it off withdraws nothing: open proposals stay on the market, and a confirmed batch can be applied again once the switch is back on. See Propose Extension for the flow itself.

Path Parameters

string
required
Market ID.

Body Parameters

boolean
required
true to switch extensions on, false to switch them off.
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. When txHash is present, every other field is ignored.

Confirm the Change

Send the mined hash back to this path as { "txHash": "0x..." }. The API checks that the transaction called setAllowExtension on the market. It then reads the offering back from the chain and updates the market record. Confirm Extension Transaction also accepts this transaction.

Response Fields

The calldata response carries the transaction twice. transaction holds to and data. The same to and data also sit directly on data, and that is where the chainId and value binding lands, so sign from those four fields.
object

Error Codes

Confirming with txHash can also return any transaction verification error.