Delete Session
Delete a single verification session — User Verification (KYC) or Business Verification (KYB) — by its session_id. The id is resolved against KYC sessions first, then KYB sessions, so both kinds are deleted through this one URL.
What happens on deletion:
- The session and its verification data are deleted, and it immediately disappears from every read endpoint:
GET /v3/session/{sessionId}/decision/returns404andGET /v3/sessions/stops listing it. - Everything the session produced goes with it: the decision, extracted data, and all related feature records (ID verification, face, liveness, face match, AML, registry checks, IP analysis, and so on).
- All stored media owned by the session is deleted: document front/back photos (full, cropped, and privacy-blurred variants), document-capture videos, portrait crops, NFC chip portrait and signature images, face reference images, liveness videos, face-match source/target images, Proof of Address documents, and any extra uploaded files (KYC); uploaded company documents and extra files (KYB). Previously issued media URLs (
https://<media-host>/...) stop resolving.
What is not affected: blocklist entries created from this session (face or document) are not removed; manage those with the blocklist endpoints. Hosted-flow share tokens already issued for the session are not revoked, and webhook deliveries already queued for it still arrive. Credits already consumed are not refunded. The parent User or Business entity is not deleted; use POST /v3/users/delete/ or POST /v3/businesses/delete/ for those.
Irreversible: deletion cannot be undone and there is no restore endpoint. Export anything you need (for example a decision PDF) before you call it.
Side effects: no webhook is emitted for deletions.
Idempotency: not idempotent at the HTTP level — the first call returns 204; repeating it returns 404 because the session no longer resolves.
Authentication: send your application’s API key in the x-api-key header; the session must belong to that application. Console user access tokens (Authorization: Bearer ...) may also call this endpoint when they carry the delete:sessions permission. Authentication and permission failures both return 403 — this API never returns 401.
Rate limit: shared write budget of 300 requests/min per API key across all POST/PATCH/DELETE endpoints; exceeding it returns 429.
To bulk-delete KYC sessions by their numeric session_number, use POST /v3/sessions/delete/ instead.
KYC and KYB support
Works for both User Verification (KYC) and Business Verification (KYB) sessions. Thesession_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
- Delete a User Verification (KYC) session
- Delete a Business Verification (KYB) session
204 No Content.Permission
Requiresdelete:sessions. The same permission covers both User Verification (KYC) and Business Verification (KYB) sessions.
Batch delete
For bulk operations, usePOST /v3/sessions/delete/ — accepts a list of session IDs of either kind.
Related
Authorizations
Path Parameters
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.
"11111111-2222-3333-4444-555555555555"
Response
Session deleted. Empty body.