Requests the deletion of a session
When to use this endpoint
- Use this endpoint to when you need to delete a session, for example you used the session to test your integration
- The endpoint is not available by default, contact your Solutions Engingeer or Veriff Customer Support to enable it for your integration
Session deletion logic
Sessions can only be deleted when they are in a final state:
created: session has been createdstarted: the end-user has entered the session flowapproved: verification was successfuldeclined: verification was declined due to some reasonresubmission_requested: additional attempt neededexpired: session expired before completionabandoned: session started but never completed
Attempting to delete the session in other statuses will respond with the
Session is not in a completed status.error messageIf session status is one of
created,startedorresubmission_requested, a decision webhook withexpired/abandonedstatus will be sentAfter successful request, session will immediately become unavailable in Veriff Customer Portal and via public API endpoints. Data will be deleted within 12 hours
Rate limiting
- This endpoint is rate limited: 10 sessions per 24 hours and 5 sessions per 1 hour
Implementation notes
- This endpoint is not available by default, contact your Solutions Engingeer or Veriff Customer Support to enable it for your integration
- This endpoint requires session-level HMAC signature authentication
- Always ensure that you use the correct API URL to send requests. See the API URL section for more info.
- The order of parameters in the real API response can differ from the order you see in this documentation. This is expected and part of the Backwards compatible changes requirements.
Your integration's API key (occasionally referred to as the "Token", "API public key" or "Publishable key"). Required for all API requests.
You can find your API key in the Veriff Customer Portal > Settings > API keys.
Session id signed with the shared secret key. Required to authenticate the request sender.
Verification session ID.
Session successfully deleted.
Session and all associated data permanently deleted.
{
"status": "success",
"verification": {
"id": "123e4567-e89b-12d3-a456-426614174000"
}
}Confirmation response after successful session deletion.
API request status
Verification object containing deleted session ID.
UUID v4 which identifies the verification session that was deleted.
Bad request - session cannot be deleted
Session must be in a completed state (approved, declined, expired, abandoned) before deletion
{
"status": "400",
"code": "1305",
"message": "Session is not in a completed status."
}Cannot delete session while end-user is actively completing verification
{
"status": "400",
"code": "1306",
"message": "Session in progress."
}HTTP status code.
Veriff-specific error code for session not completed.
Error message explaining the session must be in a final state before deletion.
HTTP status code.
Veriff-specific error code for session in progress.
Error message indicating session is currently being completed by end-user.
Unauthorized - authentication failed
{
"status": "fail",
"code": "1101",
"message": "Mandatory X-AUTH-CLIENT header containing the API key is missing from the request."
}Invalid HMAC signature
{
"status": "fail",
"code": "1812",
"message": "Signature verification failed."
}Session not found
No session found with the provided ID or session was already deleted
{
"status": "fail",
"code": "1101",
"message": "Resource not found"
}Too many requests - rate limit exceeded
Too many deletion requests sent in a short period
{
"status": "fail",
"code": "1004",
"message": "Too many requests."
}Internal server error
{
"status": "fail",
"code": "1101",
"message": "Something went wrong"
}Changelog
Date | Description |
|---|---|
Mar 9, 2026 | Documentation updated: parent categories rearranged, intro section expanded, request and response examples added |
Oct 2, 2025 |
|
Aug 6, 2025 | Response headers added |
Mar 12, 2025 | Documentation published |