KYC profile deletion
Delete a user's KYC profile record through the DALP Platform API, including who may call it, the request and response shape, and the idempotent already-removed response.
A KYC profile is a user's identity-verification record on DALP. When an account is retired or a user should no longer carry an active verification record, one Platform API call removes the profile. This endpoint deletes the profile record and reports whether one was present to delete.
This call removes the profile record itself, the entry that links a user to their verification status. Deletion does not erase every artifact the user ever submitted: previously submitted verification versions and any uploaded identity documents are retained until you remove them through their own endpoints. Treat profile deletion as retiring the active verification record, not as a single-call wipe of the complete KYC data set. To remove uploaded files, use KYC document uploads.
Deletion stays off-chain. A user's on-chain identity claims and transaction history live on the blockchain and stay in place, so removing the profile does not touch anything already written on-chain. The platform governs those on-chain records through its public-chain privacy boundaries. For how erasure requests apply across off-chain compliance records, see the privacy policy.
Who may delete a KYC profile
Deletion is sensitive, so the platform limits it to two callers: the person whose record it is, and an administrator trusted with that organization's identities. It follows the same two-path authorization the platform uses to read a profile, and a request is allowed when either path is satisfied.
| Caller | Condition |
|---|---|
| The profile owner | A user may delete their own KYC profile. The target user matches the authenticated user. |
| An organization admin | An executor holding the organization identity-manager role or the claim-issuer role for the user's system may delete that user's profile. |
A caller who is neither the profile owner nor an authorized administrator has the request rejected before any record is removed.
Delete a KYC profile
DELETE /api/v1/user/{userId}/kyc/remove removes the KYC profile for the user named in the path. Send the call with your API key, and the platform deletes the profile in a single step.
curl -X DELETE "https://your-platform.example.com/api/v1/user/usr_018f6d3e89ab7cde8123abcdefabcdef/kyc/remove" \
-H "X-Api-Key: YOUR_DALP_API_KEY"On success the response echoes the user whose profile was removed.
{
"userId": "usr_018f6d3e89ab7cde8123abcdefabcdef"
}Path parameter
| Parameter | Type | Description |
|---|---|---|
userId | string | The user whose KYC profile the request removes. |
Response field
| Field | Type | Description |
|---|---|---|
userId | string | The user whose KYC profile the request removed. |
When no profile is present
Deletion is safe to retry. The platform removes the profile and confirms in one step, so a second call, or two calls that race, cannot report a false success after the record is already gone. When no profile matches the user, the request returns 404 with DALP-0412.
| Condition | Result | What to do |
|---|---|---|
| The user has a KYC profile | The platform removes it and returns the userId. | None. The profile is gone. |
| The user has no KYC profile, or it was already removed | The request returns DALP-0412 (404). | Treat the profile as already deleted. No further step is needed. |
An already-removed profile returns DALP-0412 rather than a success. A client that needs an idempotent outcome can treat both a success response and DALP-0412 as proof that no profile remains.
When to use it
Reach for KYC profile deletion when you need to:
- Retire a user's active KYC profile record when closing or transitioning an account.
- Let a user delete their own KYC profile from a self-service account flow.
- Remove a KYC profile as an organization administrator when retiring an account.
For a complete erasure across a user's verification data, combine this call with KYC document uploads to remove stored files. To read a profile before deleting it, see KYC version submission.
KYC action request fulfillment API
Mark a reviewer's KYC change request as fulfilled once the user resubmits the requested data through the DALP Platform API, SDK, and CLI.
Private file access
How DALP restricts KYC, organisation, and admin files to authenticated Console sessions and validates each request against the caller's object-key scope.