Retrieve fraud reports by session IDs.
This endpoint accepts a list of session IDs and returns detailed information about each fraud report, including verification session data, QA reviews, and decision information.
Response Statuses Per Report: Each item in the reports array of the response will have a status:
FOUND: The fraud report was found and detailed information is provided in thedetailsfieldNOT_FOUND: The report could not be found or is not accessible. TheerrorMessagefield will contain thereason
API key
Full request path signed with the shared secret key
{
"sessionIds": [
"aca4ac5e-ea2d-40d7-9012-0e49e783eb1a",
"b1a4ac5e-ea2d-40d7-9012-0e49e783eb1b"
]
}Request body model for retrieving fraud reports by session IDs.
List of session IDs to retrieve fraud reports for (max 10 per request). Note that the reportId returned by the submit endpoint cannot be used as a retrieve key.
A session ID associated with a fraud report.
Successful Response
{
"reports": [
{
"sessionId": "ddb70e9d-ca99-4294-9716-abf3a1998cdf",
"status": "FOUND",
"details": {
"reportId": "aca4ac5e-ea2d-40d7-9012-0e49e783eb1a",
"reportedBy": "user@example.com",
"status": "Reviewed",
"verifiedAt": "2024-01-15T09:30:00Z",
"reportedAt": "2024-01-15T10:30:00Z",
"reviewedAt": "2024-01-15T11:30:00Z",
"fraudTypeReported": [
"document_is_manipulated"
],
"customerComment": "Document appears to be digitally altered",
"initialDecision": "approved",
"finalDecision": "approved",
"resetFp": false,
"reviewDecision": "declined",
"reviewOutcome": "agree",
"decisionErrorDescription": "Decision Profile Check (some_check): d07f2b48-4dc2-4470-a183-ed6032a68081: Check Result: success → QA Result: failure"
}
},
{
"sessionId": "b1b4bc6f-fb3e-41e8-a123-1f5af894fc2b",
"status": "NOT_FOUND",
"errorMessage": "Report not found or not accessible"
}
],
"processedCount": 2,
"foundCount": 1,
"notFoundCount": 1
}Response model for fraud report retrieval, providing both detailed per-item results and summary statistics for the batch operation.
Detailed results for each individual report retrieval, including status and detailed information if found.
Represents the retrieval result for a single fraud report within a batch request.
The session ID that was queried.
The retrieval status of this report ('FOUND' or 'NOT_FOUND').
Detailed fraud report information. Present only when status is 'FOUND'.
The unique identifier for this fraud report.
The user email or automation that reported this fraud.
Status of the report. 'Received' means the report was submitted but not yet reviewed, 'In Review' means a QA review is in progress, 'Reviewed' means QA review is complete.
Timestamp when the verification session was verified.
Timestamp when the fraud report was submitted.
Timestamp when the report was reviewed.
List of fraud category codes reported for this session.
A fraud category code.
Optional comment provided during reporting.
Initial decision made for this verification. 'pending' means no decision has been reached yet.
Final decision made for this verification. 'pending' means no decision has been reached yet.
Indicates if this was marked as a false positive that was reset.
The raw decision of the most recent QA review that reached a decision. 'pending' means no QA review has reached a decision yet.
Agreement verdict. 'agree' means the QA review changed the decision, so Veriff confirms the reported fraud. 'disagree' means the QA review reached the same decision, so the fraud claim was rejected. 'pending' means there is no QA decision yet or no initial decision to compare against.
Description of any decision errors if applicable.
Error message if the report was not found. Present only when status is 'NOT_FOUND'.
Total number of session IDs processed in this request.
Number of reports that were successfully found.
Number of reports that were not found or not accessible.
Bad Request. Possible reasons: Invalid request format, no session IDs provided, or more than 10 session IDs provided.
Generic error response structure.
A machine-readable error code indicating the type of error.
A human-readable message explaining the error.
Unauthorized. Possible reasons: Invalid API key or signature.
Generic error response structure.
A machine-readable error code indicating the type of error.
A human-readable message explaining the error.
Unprocessable Entity. Input validation failed.
Generic error response structure.
A machine-readable error code indicating the type of error.
A human-readable message explaining the error.
Too Many Requests. Rate limit exceeded.
Generic error response structure.
A machine-readable error code indicating the type of error.
A human-readable message explaining the error.
Internal Server Error. An unexpected error occurred.
Generic error response structure.
A machine-readable error code indicating the type of error.
A human-readable message explaining the error.
Changelog
Date | Description |
|---|---|
Aug 24, 2026 | - Request body examples with sample session IDs added - Clarification added that - Four new required fields in response payload: - - |
Dec 19, 2025 | VRF-AUTH-CLIENT header description updated |
Nov 28, 2025 | Response payload example added |
Nov 26, 2025 | Example data for decisionErrorDescription added |
Nov 6, 2025 | Documentation published |