Skip to main content
POST
Records your decision to accept an opened KYC record, and returns one unsigned setListed transaction for each whitelist bound to the record’s source. The owner or a manager of the whitelist signs and broadcasts each one, then Confirm Record Admission records the result. Trusset holds no key and sends nothing. A record can be approved only after your tool opened it, so the file is on your side before you decide. Trusset never sees the file and takes no part in the decision.

What approving does

  • The record becomes APPROVED. From now until validUntil, Set Whitelist Members accepts the record’s wallet on the whitelists bound to its source.
  • An earlier APPROVED record from the same source for the same wallet becomes SUPERSEDED.
  • A customer.kyc_record_approved event goes to your customer webhooks.
  • Nothing changes on chain. The wallet is listed only when your wallet signs the transaction in admissions[].plan.
Calling this again for an APPROVED record changes nothing and returns the admissions again. Use that to fetch the transaction later, or to build it for another signer.
The approval is recorded before the transactions are built. When a build fails, for example with NOT_ACCESS_LIST_MANAGER because the signer cannot change the list, the call answers with that error and the record is APPROVED all the same. Fix the cause and call again to get the admissions.

Path Parameters

string
required
The record id from List KYC Records.

Body Parameters

string
The wallet that will sign: the owner or a manager of the bound whitelists. Omitted, the first verified wallet of your instance that is the owner or a manager of the list is used. See Who signs.

Response Fields

object
plan.confirmWith names the confirm route of this record and the listId to send with the transaction hash. Confirm Record Admission verifies the transaction, checks that it listed this record’s wallet, and writes the admission to the customer audit log next to the record.

Error Codes