Skip to main content
DELETE
curl

KYC and KYB support

Works for both User Verification (KYC) and Business Verification (KYB) sessions. The session_id is resolved against both session types; the same delete behavior applies to both.

Behavior

  • The session is deleted, together with its decision, its extracted data, its associated feature records (ID verifications, registry checks, documents, AML, IP analysis, and so on) and all of its stored media.
  • The session disappears from list and decision responses immediately, and media URLs issued before the call stop resolving.
  • Deletion is irreversible. There is no restore endpoint, so export anything you need, such as a decision PDF, before you call it.

What is not affected

Deleting a session does not clean these up for you. If you are handling a right-to-erasure request, account for them separately.
  • Blocklist entries created from the session (face or document) stay in place. Remove them from the blocklist.
  • Hosted-flow share tokens already issued for the session are not revoked.
  • Webhook deliveries already queued still arrive, and no webhook is emitted for the deletion itself.
  • Credits already consumed by the verification are not refunded.
  • The parent User or Business entity is not deleted. Use Delete Users or Delete Businesses for those.

Examples

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 (session_id) of the User Verification (KYC) or Business Verification (KYB) session to delete, as returned when the session was created. Must be a canonical hyphenated UUID — a non-UUID value does not match the route and returns 404.

Example:

"11111111-2222-3333-4444-555555555555"

Response

Session deleted. Empty body.