Skip to main content
POST
Confirm Document
Confirms a mined setDocument or removeDocument transaction. The server reads the receipt itself: the transaction must target the document registry, call setDocument or removeDocument, be signed by a verified wallet of your instance, and emit DocumentUpdated or DocumentRemoved for this market. What is recorded comes from those events, never from the request. The confirm marks staged loan documents recorded when an event carries their loan, name, hash and locator, and writes one audit entry per event. Confirming the same transaction again changes nothing and writes no second audit entry. A transaction signed through a smart account that wraps the call is verified through the wrapped call.

Path Parameters

string
required
The market’s record ID on your instance.

Body Parameters

string
required
The hash of the mined transaction.

Response Fields

object

Error Codes