Skip to main content
POST
Records a settlement you have broadcast. Trusset reads the receipt and checks that the transaction was mined, succeeded, targeted the custody contract, called the expected settlement function, and settled exactly the buyers, sellers, tokens, amounts and trade references this settlement covers. Only then is anything written. State is derived from the receipt, never from the request body. A confirm call that fails verification changes nothing. Confirming is what releases the trade from the queue: the settlement and its trades are marked CONFIRMED, and each side’s reservation is reduced by what actually settled rather than by what was reserved.

Idempotency

Accepts an optional Idempotency-Key header. Confirming an already-confirmed settlement is safe regardless: it returns the recorded result with alreadyConfirmed: true and does not touch state.

Path Parameters

string
required
Settlement ID.

Body Parameters

string
required
Hash of the settlement transaction you broadcast. Must be a 32-byte hex string.

Response Fields

object

When confirmation fails

A reverted transaction moved nothing, so the settlement and its trades are marked FAILED and the trade is unwound: the fill is reversed and both reservations are released. The orders are free again, and the traders can sign fresh ones. TX_NOT_FOUND is treated differently. The transaction may simply be unmined, so the settlement is marked failed but not unwound, since unwinding a trade whose transaction later lands would double-count it. Wait for a confirmation and call again.
TX_NOT_FOUND is the expected answer when you confirm too early. Wait for one confirmation and retry rather than treating it as a failure.

Error Codes