Skip to main content
A blockchain contact is a saved external wallet: a named address on a specific chain, such as a customer’s or vendor’s wallet. After your API user approves it, reference the contact by its id with type: "CONTACT" as the destination of a transfer or payout, or as the source of an LP vault deposit. Each Contact records:
  • Address: name, blockChain, and address.
  • Permitted assets: assetList, the assets the contact can be used with.
  • Your references: tags and externalId. Filter lists by name, status, or externalId. See Filtering and Pagination.
  • Screening: isSanctioned, whether the address is flagged by sanctions screening.
To keep a contact inside a sub-org, pass subOrgId when you create it.
Lifecycle: Creating or updating a contact needs your API user’s approval. The contact stays PENDING until it’s approved, then moves to APPROVED or DECLINED. See Approvals. After creation, you can change only assetList and contactGroupIds; a contact’s name and address can’t be changed.

List contacts

GET /api/external/contacts/

Retrieve a contact

GET /api/external/contacts/{contactId}/

Create a contact

POST /api/external/contacts/

Update a contact

PUT /api/external/contacts/{contactId}/