Contacts API

Contacts store named EVM wallet addresses for the authenticated user. You use them to reduce copy-paste errors when operators reuse recipients in issuance, settlement, servicing, and transfer workflows. They support API and dapp address-book workflows. They do not represent identity verification, KYC status, token permissions, or transfer approval rules.

Prerequisites

You need:

• an authenticated DALP API request with access to the contacts routes
• a valid EVM wallet address for each contact
• a name from 1 to 120 characters

The dapp exposes the same primitive under Contacts. The contacts list lets you search saved names and wallets. The contact detail page shows the saved name, wallet, creation time, and update time, and lets you edit or delete the entry.

Quickstart: create a reusable contact

Create a contact by sending a name and wallet address. The platform validates the wallet as an EVM address and returns the saved contact in a response envelope.

curl -X POST https://your-platform.example.com/api/v2/contacts \
  -H "X-Api-Key: sm_dalp_xxxxxxxxxxxxxxxx" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Northwind Treasury",
    "wallet": "0x71C7656EC7ab88b098defB751B7401B5f6d8976F"
  }'

{
  "data": {
    "id": "8a3b8a14-8d50-4a52-a7db-2f4a7c2a8e5f",
    "name": "Northwind Treasury",
    "wallet": "0x71C7656EC7ab88b098defB751B7401B5f6d8976F",
    "createdAt": "2026-05-17T09:10:29.428Z",
    "updatedAt": "2026-05-17T09:10:29.428Z"
  },
  "links": {
    "self": "/v2/contacts/8a3b8a14-8d50-4a52-a7db-2f4a7c2a8e5f"
  }
}

If you omit id and submit a wallet that already exists in your contacts, DALP updates that existing contact name instead of creating a duplicate. If you include id, DALP updates that specific contact.

Contact model

Contacts are convenience data. They do not prove that a wallet belongs to a participant, investor, custodian, or legal entity.

Endpoint reference

Existing integrations that still call /api/contacts, /api/contacts/{id}, or /api/contacts/search can continue to call those routes. New integrations should use /api/v2/contacts.

List and search contacts

Use the list endpoint for contacts screens and recipient pickers.

curl --globoff "https://your-platform.example.com/api/v2/contacts?page[offset]=0&page[limit]=50&sort=name" \
  -H "X-Api-Key: sm_dalp_xxxxxxxxxxxxxxxx"

{
  "data": [
    {
      "id": "8a3b8a14-8d50-4a52-a7db-2f4a7c2a8e5f",
      "name": "Northwind Treasury",
      "wallet": "0x71C7656EC7ab88b098defB751B7401B5f6d8976F",
      "createdAt": "2026-05-17T09:10:29.428Z",
      "updatedAt": "2026-05-17T09:10:29.428Z"
    }
  ],
  "meta": {
    "total": 1
  },
  "links": {
    "self": "/v2/contacts?page[offset]=0&page[limit]=50&sort=name",
    "first": "/v2/contacts?page[offset]=0&page[limit]=50&sort=name",
    "prev": null,
    "next": null,
    "last": "/v2/contacts?page[offset]=0&page[limit]=50&sort=name"
  }
}

You can order contacts by createdAt, updatedAt, name, or wallet. The default order is createdAt.

Use global search when an operator enters a name or wallet fragment. DALP searches the authenticated user's contact names and wallet addresses only.

curl --globoff "https://your-platform.example.com/api/v2/contacts?filter[q]=northwind" \
  -H "X-Api-Key: sm_dalp_xxxxxxxxxxxxxxxx"

Read, update, and delete one contact

Read a contact before you show a detail view or confirm a destructive action.

curl https://your-platform.example.com/api/v2/contacts/8a3b8a14-8d50-4a52-a7db-2f4a7c2a8e5f \
  -H "X-Api-Key: sm_dalp_xxxxxxxxxxxxxxxx"

{
  "data": {
    "id": "8a3b8a14-8d50-4a52-a7db-2f4a7c2a8e5f",
    "name": "Northwind Treasury",
    "wallet": "0x71C7656EC7ab88b098defB751B7401B5f6d8976F",
    "createdAt": "2026-05-17T09:10:29.428Z",
    "updatedAt": "2026-05-17T09:10:29.428Z"
  },
  "links": {
    "self": "/v2/contacts/8a3b8a14-8d50-4a52-a7db-2f4a7c2a8e5f"
  }
}

Update a contact by including its id in the POST /api/v2/contacts body.

curl -X POST https://your-platform.example.com/api/v2/contacts \
  -H "X-Api-Key: sm_dalp_xxxxxxxxxxxxxxxx" \
  -H "Content-Type: application/json" \
  -d '{
    "id": "8a3b8a14-8d50-4a52-a7db-2f4a7c2a8e5f",
    "name": "Northwind Settlement Treasury",
    "wallet": "0x71C7656EC7ab88b098defB751B7401B5f6d8976F"
  }'

The dapp detail page uses this same update behavior. The Edit action opens a sheet with name and wallet fields, validates the wallet address, trims the submitted values, and saves the changed contact.

Delete a contact when the saved entry is no longer useful.

curl -X DELETE https://your-platform.example.com/api/v2/contacts/8a3b8a14-8d50-4a52-a7db-2f4a7c2a8e5f \
  -H "X-Api-Key: sm_dalp_xxxxxxxxxxxxxxxx"

Deleting a contact removes only the address-book entry. It does not change token balances, identities, claims, transfer approvals, custody rules, or historical transaction evidence.

Review a contact in the dapp

Operators can open a contact from the Contacts area to review its detail page before reusing the wallet address in another workflow. The detail page shows a breadcrumb back to Contacts, the contact display name, contact and address book badges, the wallet address in a copyable badge, and the created and updated timestamps.

The basic information card includes the contact edit and delete actions. Editing opens the contact sheet on the detail page. Deleting the contact refreshes the Contacts list and global search results, then returns the operator to Contacts. If the contact cannot be read, the dapp returns the operator to Contacts.

For step-by-step operator instructions, see Review address book contacts.

Errors and retry behavior

Production requirements

For production integrations:

1. Treat a contact selection as an address lookup, not an authorization decision.
2. Resolve the selected contact to its wallet address before submitting a token operation.
3. Let the token operation enforce identity, compliance, freeze, approval, role, and custody checks.
4. Display the wallet address at confirmation time so an operator can verify the recipient.
5. Read the final token operation result from the relevant transaction, action, or servicing workflow.

This separation keeps contacts useful for operator accuracy without moving compliance decisions into address-book data.

Compliance and audit scope

Contacts are scoped to the authenticated user. They contain a display name, an EVM wallet address, and timestamps. They are not participant records, identity claims, KYC results, sanctions-screening outputs, custody mandates, or legal ownership records.

Auditors should treat contact history as operator convenience evidence only. The controls that determine whether a mint, transfer, burn, forced transfer, or servicing action can execute live on the asset, identity, approval, compliance, custody, and role paths for that operation.

Related guides

• Error handling
• Token holders and transfers
• Developer guides