Skip to main content
DELETE
/
v3
/
session
/
{sessionId}
/
delete
curl
curl -X DELETE \
  https://verification.didit.me/v3/session/11111111-2222-3333-4444-555555555555/delete/ \
  -H 'Authorization: Bearer YOUR_CLIENT_TOKEN'
{
  "detail": "Authentication credentials were not provided."
}

Documentation Index

Fetch the complete documentation index at: https://docs.didit.me/llms.txt

Use this file to discover all available pages before exploring further.

​
Session kind

Works for both User Verification (KYC) and Business Verification (KYB) sessions. The session_id is looked up in both tables; the same delete behavior applies to both.

​
Behavior

  • Session is deleted — deleted_at is set. The row remains in the database for your configured data retention window, then is hard-deleted.
  • Associated feature records (ID verifications, registry checks, documents, etc.) are deleted alongside.
  • Links to the parent entity (User or Business) are preserved in history but the session itself no longer appears in list responses.

​
Examples

curl -X DELETE https://verification.didit.me/v3/session/4c5c7f3a-.../delete/ \
  -H "x-api-key: YOUR_API_KEY"
Response: 204 No Content.

​
Permission

Requires delete:sessions. The same permission covers both User Verification (KYC) and Business Verification (KYB) sessions.

​
Batch delete

For bulk operations, use POST /v3/sessions/delete/ — accepts a list of session IDs of either kind.

Authorizations

​
x-api-key
string
header
required

Path Parameters

​
sessionId
string<uuid>
required

UUID of the User Verification (KYC) or Business Verification (KYB) session to delete.

Example:

"11111111-2222-3333-4444-555555555555"

Response

Session soft-deleted. Empty body.