Configure trusted issuers

For the web interface approach, see the user guide.

Prerequisites

• Platform URL (e.g., https://your-platform.example.com)
• API key from a user with the Claim Policy Manager role (see Getting Started for API key setup)
• Wallet verification method enabled on your account (e.g., pincode or 2FA)
• Understanding of your compliance requirements
• Wallet address of the user you want to make a trusted issuer

About trusted issuers

Trusted issuers are identity addresses authorized in the active system's trusted issuer registry. Assets that use identity verification rules rely on these issuers when checking whether a wallet has a claim for the required topic. For background on how the verification system works, see Compliance Overview.

Available verification topics

The platform includes preset verification topics for common compliance scenarios. Each topic has a unique topicId and a signature that defines the claim data structure.

Investor verification topics

Issuer verification topics

Asset verification topics

Managing system claim topics

Use claim topic mutations only when the platform needs a new or changed claim data shape. Existing asset and compliance flows usually rely on the preset topics above.

To create a claim topic, send a human-readable name, a comma-separated ABI type list in signature, and wallet verification:

curl -X POST "https://your-platform.example.com/api/v2/system/claim-topics" \
  -H "X-Api-Key: [REDACTED]" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "assetOrigin",
    "signature": "string,uint256",
    "walletVerification": {
      "secretVerificationCode": "[REDACTED]"
    }
  }'

The API normalizes the signature to the parenthesized ABI form on-chain. Send string,uint256, not (string,uint256).

To change the data shape for an existing topic, use PUT /api/v2/system/claim-topics/{name} with the replacement signature and wallet verification. To remove a topic scheme, use DELETE /api/v2/system/claim-topics/{name} with wallet verification.

Configuring trusted issuers

curl -X GET "https://your-platform.example.com/api/system/identity/by-wallet/0x742d35Cc6634C0532925a3b844Bc9e7595f0bEb" \
  -H "X-Api-Key: YOUR_API_KEY"

{
  "id": "0x8e5F72f6E5b3B4D1234567890AbCdEf1234567890",
  "account": {
    "id": "0x742d35Cc6634C0532925a3b844Bc9e7595f0bEb",
    "contractName": null
  },
  "isContract": false,
  "hasIdentity": true,
  "claims": []
}

curl -X GET "https://your-platform.example.com/api/v2/system/claim-topics" \
  -H "X-Api-Key: YOUR_API_KEY"

[
  {
    "id": "0x534b8f03c16c92c70d1da1d2fae43b98352bf3d7...",
    "topicId": "26984799302505749158794800959285050858086405868089409909048783980951278841746",
    "name": "knowYourCustomer",
    "signature": "string claim",
    "registry": {
      "id": "0x534b8f03c16c92c70d1da1d2fae43b98352bf3d7"
    }
  },
  {
    "id": "0x534b8f03c16c92c70d1da1d2fae43b98352bf3d7...",
    "topicId": "15733030998618876990024220391915773205162379317494393310546829862321881862123",
    "name": "accreditedInvestor",
    "signature": "string claim",
    "registry": {
      "id": "0x534b8f03c16c92c70d1da1d2fae43b98352bf3d7"
    }
  },
  {
    "id": "0x534b8f03c16c92c70d1da1d2fae43b98352bf3d7...",
    "topicId": "39526553109170329799339511574661256630735485618560740361645615581310848276505",
    "name": "qualifiedInstitutionalInvestor",
    "signature": "string claim",
    "registry": {
      "id": "0x534b8f03c16c92c70d1da1d2fae43b98352bf3d7"
    }
  }
  // ... additional topics available
]

curl -X POST "https://your-platform.example.com/api/v2/system/trusted-issuers" \
  -H "X-Api-Key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "issuerAddress": "0x8e5F72f6E5b3B4D1234567890AbCdEf1234567890",
    "claimTopicIds": [
      "26984799302505749158794800959285050858086405868089409909048783980951278841746",
      "15733030998618876990024220391915773205162379317494393310546829862321881862123"
    ],
    "walletVerification": {
      "secretVerificationCode": "YOUR_PINCODE"
    }
  }'

{
  "data": {
    "txHash": "0x1234567890abcdef...",
    "issuerAddress": "0x8e5F72f6E5b3B4D1234567890AbCdEf1234567890"
  },
  "meta": {
    "txHashes": ["0x1234567890abcdef..."]
  },
  "links": {
    "self": "/v2/system/trusted-issuers"
  }
}

curl --globoff -X GET "https://your-platform.example.com/api/v2/system/trusted-issuers?filter[id]=0x8e5F72f6E5b3B4D1234567890AbCdEf1234567890&page[offset]=0&page[limit]=25" \
  -H "X-Api-Key: YOUR_API_KEY"

{
  "data": [
    {
      "id": "0x8e5F72f6E5b3B4D1234567890AbCdEf1234567890",
      "account": null,
      "claimTopics": [
        {
          "id": "0x534b8f03c16c92c70d1da1d2fae43b98352bf3d7...",
          "topicId": "26984799302505749158794800959285050858086405868089409909048783980951278841746",
          "name": "knowYourCustomer",
          "signature": "string claim"
        },
        {
          "id": "0x534b8f03c16c92c70d1da1d2fae43b98352bf3d7...",
          "topicId": "15733030998618876990024220391915773205162379317494393310546829862321881862123",
          "name": "accreditedInvestor",
          "signature": "string claim"
        }
      ],
      "deployedInTransaction": "0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef",
      "isGlobal": false
    }
  ],
  "meta": {
    "total": 1,
    "facets": {}
  },
  "links": {
    "self": "/v2/system/trusted-issuers?sort=id&filter%5Bid%5D=0x8e5F72f6E5b3B4D1234567890AbCdEf1234567890&page%5Boffset%5D=0&page%5Blimit%5D=25",
    "first": "/v2/system/trusted-issuers?sort=id&filter%5Bid%5D=0x8e5F72f6E5b3B4D1234567890AbCdEf1234567890&page%5Boffset%5D=0&page%5Blimit%5D=25",
    "prev": null,
    "next": null,
    "last": "/v2/system/trusted-issuers?sort=id&filter%5Bid%5D=0x8e5F72f6E5b3B4D1234567890AbCdEf1234567890&page%5Boffset%5D=0&page%5Blimit%5D=25"
  }
}

Token-level trusted issuers

Use token-level trusted issuers when one asset needs a narrower or different issuer policy than the platform default. The token list endpoint returns the resolved token -> system -> global chain so an integration can see which issuers are token-specific and which issuers are inherited from the system or global registry.

List token trusted issuers

curl --globoff -X GET "https://your-platform.example.com/api/v2/tokens/0x1234567890AbCdEf1234567890AbCdEf1234567890/trusted-issuers?filter[source]=token&page[offset]=0&page[limit]=25" \
  -H "X-Api-Key: YOUR_API_KEY"

Use filter[source] to limit results to token, system, or global. Use filter[q] to search by issuer account address. The response is paginated and includes meta.total, meta.facets, and meta.hasTrustedIssuersRegistry.

{
  "data": [
    {
      "id": "0x8e5F72f6E5b3B4D1234567890AbCdEf1234567890",
      "account": { "id": "0x742d35Cc6634C0532925a3b844Bc9e7595f0bEb" },
      "inheritanceLevel": "token",
      "registry": { "id": "0x4567890AbCdEf1234567890AbCdEf1234567890123" },
      "isInheritedElsewhere": false,
      "claimTopics": [
        {
          "topicId": "26984799302505749158794800959285050858086405868089409909048783980951278841746",
          "name": "knowYourCustomer"
        }
      ]
    }
  ],
  "meta": {
    "total": 1,
    "facets": {},
    "hasTrustedIssuersRegistry": true
  },
  "links": {
    "self": "/v2/tokens/0x1234567890AbCdEf1234567890AbCdEf1234567890/trusted-issuers?filter%5Bsource%5D=token&page%5Boffset%5D=0&page%5Blimit%5D=25",
    "first": "/v2/tokens/0x1234567890AbCdEf1234567890AbCdEf1234567890/trusted-issuers?filter%5Bsource%5D=token&page%5Boffset%5D=0&page%5Blimit%5D=25",
    "prev": null,
    "next": null,
    "last": "/v2/tokens/0x1234567890AbCdEf1234567890AbCdEf1234567890/trusted-issuers?filter%5Bsource%5D=token&page%5Boffset%5D=0&page%5Blimit%5D=25"
  }
}

Add a token trusted issuer

curl -X POST "https://your-platform.example.com/api/v2/tokens/0x1234567890AbCdEf1234567890AbCdEf1234567890/trusted-issuers" \
  -H "X-Api-Key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "issuerAddress": "0x8e5F72f6E5b3B4D1234567890AbCdEf1234567890",
    "claimTopicIds": [
      "26984799302505749158794800959285050858086405868089409909048783980951278841746"
    ],
    "walletVerification": {
      "secretVerificationCode": "YOUR_PINCODE"
    }
  }'

issuerAddress is the issuer identity contract address, not the issuer's EOA wallet address. claimTopicIds must contain at least one decimal-string topic ID and can contain at most 50 topic IDs. The response is an asynchronous blockchain mutation response with txHash and issuerAddress; refresh the list after indexer pickup to confirm the row appears with inheritanceLevel: "token".

Remove a token trusted issuer

curl -X DELETE "https://your-platform.example.com/api/v2/tokens/0x1234567890AbCdEf1234567890AbCdEf1234567890/trusted-issuers/0x8e5F72f6E5b3B4D1234567890AbCdEf1234567890" \
  -H "X-Api-Key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "walletVerification": {
      "secretVerificationCode": "YOUR_PINCODE"
    }
  }'

The delete endpoint only removes token-level rows. If the issuer is inherited from the system or global registry, the token endpoint returns a not-found error and does not remove the inherited issuer from the effective chain. If isInheritedElsewhere is true on a token row, removing that token row leaves the parent-tier trust visible in the resolved list.

Managing trusted issuers

Add or remove one topic atomically

Use the single-topic endpoints when your integration needs to add or remove one verification topic without replacing the issuer's full topic list:

curl -X POST "https://your-platform.example.com/api/v2/system/trusted-issuers/0x8e5F72f6E5b3B4D1234567890AbCdEf1234567890/claim-topics/26984799302505749158794800959285050858086405868089409909048783980951278841746" \
  -H "X-Api-Key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "walletVerification": {
      "secretVerificationCode": "YOUR_PINCODE"
    }
  }'

Use DELETE on the same path to remove the topic from that issuer. These endpoints compute the next topic list server-side, so a single-topic add or remove does not overwrite unrelated topics that are already assigned to the issuer.

The response includes issuerAddress, topicId, and txHash. If the requested add is already present, or the requested remove is already absent, the call is idempotent and returns an empty txHash instead of submitting another on-chain update.

Update issuer topics

To replace the full set of verification topics for an issuer:

curl -X PATCH "https://your-platform.example.com/api/v2/system/trusted-issuers/0x8e5F72f6E5b3B4D1234567890AbCdEf1234567890" \
  -H "X-Api-Key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "claimTopicIds": [
      "26984799302505749158794800959285050858086405868089409909048783980951278841746",
      "15733030998618876990024220391915773205162379317494393310546829862321881862123",
      "39526553109170329799339511574661256630735485618560740361645615581310848276505"
    ],
    "walletVerification": {
      "secretVerificationCode": "YOUR_PINCODE"
    }
  }'

Response:

{
  "txHash": "0xabcdef1234567890...",
  "issuerAddress": "0x8e5F72f6E5b3B4D1234567890AbCdEf1234567890"
}

Remove trusted issuer

To revoke an issuer's trusted status:

curl -X DELETE "https://your-platform.example.com/api/v2/system/trusted-issuers/0x8e5F72f6E5b3B4D1234567890AbCdEf1234567890" \
  -H "X-Api-Key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "walletVerification": {
      "secretVerificationCode": "YOUR_PINCODE"
    }
  }'

Response:

{
  "txHash": "0x9876543210fedcba...",
  "issuerAddress": "0x8e5F72f6E5b3B4D1234567890AbCdEf1234567890"
}

Before DALP submits the removal transaction, it checks the indexed trusted-issuer registry.

If the issuer is not registered for the active system, the API returns SYSTEM_TRUSTED_ISSUER_NOT_FOUND and does not queue the on-chain call.

Get topic details with trusted issuers

Get full details for a specific claim topic, including its trusted issuers:

curl -X GET "https://your-platform.example.com/api/v2/system/claim-topics/knowYourCustomer" \
  -H "X-Api-Key: YOUR_API_KEY"

Response:

{
  "id": "0x534b8f03c16c92c70d1da1d2fae43b98352bf3d7...",
  "name": "knowYourCustomer",
  "signature": "string claim",
  "topicId": "26984799302505749158794800959285050858086405868089409909048783980951278841746",
  "trustedIssuers": [
    {
      "id": "0x8e5F72f6E5b3B4D1234567890AbCdEf1234567890",
      "addedAt": "2024-01-15T10:30:00Z",
      "revokedAt": "1970-01-01T00:00:00Z",
      "account": {
        "id": "0x742d35Cc6634C0532925a3b844Bc9e7595f0bEb"
      }
    }
  ]
}

The response includes full topic details along with all non-revoked trusted issuers authorized for that topic.

List claim topics for a trusted issuer

Get the full topic list for a specific trusted issuer identity:

curl -X GET "https://your-platform.example.com/api/v2/system/trusted-issuers/0x8e5F72f6E5b3B4D1234567890AbCdEf1234567890/topics" \
  -H "X-Api-Key: YOUR_API_KEY"

Response:

{
  "issuerAddress": "0x8e5F72f6E5b3B4D1234567890AbCdEf1234567890",
  "claimTopics": [
    {
      "id": "0x534b8f03c16c92c70d1da1d2fae43b98352bf3d7...",
      "topicId": "26984799302505749158794800959285050858086405868089409909048783980951278841746",
      "name": "knowYourCustomer",
      "signature": "string claim"
    }
  ]
}

Request parameters

Create claim topic

Update claim topic

PUT /api/v2/system/claim-topics/{name} updates the topic signature. Send the replacement signature without parentheses.

Delete claim topic

DELETE /api/v2/system/claim-topics/{name} removes the named topic scheme from the system claim topic registry.

List system trusted issuers

GET /api/v2/system/trusted-issuers accepts standard collection query parameters. Results are returned in identity-address order by default:

Create system trusted issuer

Update system trusted issuer

PATCH /api/v2/system/trusted-issuers/{issuerAddress} replaces the issuer's topic set with the supplied claimTopicIds array. Use the single-topic routes below when you only need to add or remove one topic without resending the complete set.

Delete system trusted issuer

Get topic details (with trusted issuers)

List claim topics for issuer

GET /api/v2/system/trusted-issuers/{issuerAddress}/topics lists the claim topics currently assigned to one trusted issuer.

Add or remove one claim topic

Use these routes when the issuer already exists and you want to mutate a single topic assignment:

• POST /api/v2/system/trusted-issuers/{issuerAddress}/claim-topics/{topicId} adds one topic to the issuer.
• DELETE /api/v2/system/trusted-issuers/{issuerAddress}/claim-topics/{topicId} removes one topic from the issuer.

Both routes require walletVerification in the request body and return the same blockchain mutation response shape as other trusted-issuer mutations. Adding a topic that is already present, or removing one that is already absent, is treated as idempotent and may return no transaction hash.

Token trusted issuers

filter[source] accepts token, system, or global. Token create requests accept 1 to 50 claimTopicIds; each ID must be a non-negative decimal string that fits uint256. Create requests can return DALP-4001, DALP-4003, or DALP-4214; delete requests can return DALP-4001 or DALP-4003.

Wallet verification object

Response fields

Trusted issuers list

GET /api/v2/system/trusted-issuers returns a paginated object:

Trusted issuer

Token trusted issuer row

Verification topic

In trusted issuer response (claimTopics array):

In claim topics endpoint (GET /api/v2/system/claim-topics):

Includes all fields above plus:

Best practices

Issuer selection criteria

Choose trusted issuers based on:

• Authority - Legal or professional standing
• Expertise - Knowledge of verification area
• Independence - Avoid conflicts of interest
• Reliability - Consistent and accurate

Topic assignment principles

• Segregation - Separate issuer types by domain
• Redundancy - Multiple issuers for critical topics
• Specialization - Match expertise to topics
• Compliance - Follow regulatory requirements

Operational considerations

1. Regular audits - Review issuer activities
2. Rotation - Periodically update issuers
3. Training - Ensure issuers understand responsibilities
4. Documentation - Record issuer selection rationale

Troubleshooting

Related guides

• Compliance Overview - Complete compliance reference
• Verify KYC - Issue verifications via API
• Claims and identity - Understand claim topics, trusted issuers, and identity checks
• Add Administrators - Grant roles via API
• Configure Trusted Issuers (User Guide) - Web interface approach