Skip to main content
PATCH
Changes your instance’s record of a whitelist: its name, its purpose, or whether it is archived. Nothing is signed and nothing changes on chain, so the list keeps its owner, its managers and its members. Only the instance that keeps the record can update it. A list another instance keeps answers 404. The change is written to the audit log as LENDING_ACCESS_LIST_RECORD_UPDATED.
Archiving hides the record and stops the list from being named by its ID as a new gate. A list that still gates a market, vault or vault group of your instance cannot be archived: the call answers ACCESS_LIST_IN_USE and names those gates in details.usedBy. Install another whitelist or a register there first. Archiving never changes the list on chain: its owner and managers can still list and remove wallets, and a product of another instance that installed it keeps admitting its members.

What the purpose decides

purpose is checked when a list is installed as a gate, by Set Identity Gates, Deploy Market, Accept Lender Role and vault and vault group creation in the issuer app. A list kept for DEPOSITOR is refused as a borrower gate, and one kept for BORROWER as a provider or depositor gate, with ACCESS_LIST_PURPOSE_MISMATCH. The same check runs on this call. A purpose that contradicts a gate the list already fills on a market, vault or vault group of your instance is refused with ACCESS_LIST_PURPOSE_MISMATCH (409), and details.usedBy names those gates. ANY is always accepted, and so is a purpose that matches every gate the list fills, which is how a list installed under the wrong purpose is put right.

Path Parameters

string
required
The whitelist ID from List Whitelists.

Body Parameters

Send at least one of the three fields.
string
New display name, 3 to 64 characters after trimming.
string
BORROWER, DEPOSITOR or ANY.
boolean
true archives the record, false restores it.

Response Fields

object

Error Codes