Skip to main content
The manage sub-module handles customer CRUD operations, search, and wallet linking. All operations are scoped to the instance bound to your API key.

Create a customer

Customers can be created with or without a wallet address. When no wallet is provided, the system generates a referenceKey that you can use to link a wallet later.
If the wallet address is already registered on-chain in the IdentityRegistry, the customer status is automatically set to verified. The SDK provides typed search methods that map to different lookup strategies. Each returns a single Customer object or throws a TrussetError with code NOT_FOUND.

List customers

Update

Only provided fields are updated. Omitted fields remain unchanged. For customers created without a wallet address, link one using the referenceKey:
The wallet address must not already be assigned to another customer in the same instance. If the address is already verified on-chain, the customer status updates to verified automatically.

Archive

Archiving soft-deletes a customer. Archived customers are excluded from list queries by default.

Linked wallets

A customer has one primary wallet and any number of linked wallets. Linked wallets resolve to the same customer in lookups and country checks. A wallet can only belong to one customer per instance.
Conflicts return 409 with a specific code: ALREADY_PRIMARY, WALLET_ALREADY_LINKED (same customer), or WALLET_IN_USE (another customer).

Batch country lookup

Retrieve country codes for a list of wallet addresses in a single call. Useful for compliance checks across large holder sets.
Addresses without a matching customer record are omitted from the result.