Fetch BGV Report (JSON)
Fetch the background verification report for a case as structured JSON instead of a PDF. Call this endpoint after submitting a candidate via BGVSubmitViewV2 to check progress and view results using the case_id returned in data.cases_created[].case_id.
The report is available as soon as the case exists — check data.status to know whether results are still in progress or final.
Overview
Fetch the background verification report for a BGV case as structured JSON instead of a PDF. Call this endpoint with thecase_id returned by the Submit Candidates for BGV (Bulk) endpoint to check progress and read results directly in your own application.
When to Call This Endpoint
data.status on each call to know whether the case is still in_progress, under review (in_audit), or completed. Within a case, individual checks may also still show result: "pending" even after others have finished — don’t treat a 200 response alone as a sign that verification is done.
Poll on a backoff interval (for example 30s → 60s → 5m) rather than continuously. Avoid polling more than once every 15 seconds.
Response Format
| Field | Description |
|---|---|
reference_id | Reference number for the case. |
generated_at | Timestamp for this report snapshot. |
status | Case status: in_progress, in_audit, or completed. |
result | Overall result for the case (see below). |
candidate | { name, photo } for the candidate. |
summary | Count of checks by result. |
checks | List of requested checks with their individual results. |
Result values
| Value | Meaning |
|---|---|
clear | Verified with no issues. |
minor_discrepancy | A small, non-blocking mismatch. |
discrepancy | A material mismatch requiring attention. |
unable_to_verify | The check could not reach a conclusion. |
not_available | Not enough information was available to perform the check. |
pending | The check has not finished yet. |
Each item in checks
| Field | Description |
|---|---|
type | Check type, e.g. identity_aadhaar, criminal, employment. |
name | Display name, e.g. “Aadhaar Verification”. |
category | Display group, e.g. “Identity”, “Criminal & Compliance”. |
status | in_progress or completed. |
result | One of the result values above. |
completed_at | When the check finished, or null if not yet. |
fields | Verified details (name, DOB, masked ID number, etc.), where applicable. |
documents | Document/report page image URLs, where applicable. |
remark | A short note about the outcome, where applicable. |
entries | Per-item results for multi-part checks (employment, reference, address, social/professional), where applicable. |
Authorizations
API key issued by KonnectNXT. Pass as Authorization: Bearer <your_api_key>.
Query Parameters
UUID of the case to fetch. Obtained from the BGVSubmitViewV2 response (data.cases_created[].case_id).
"6bc26096-dfe5-4c44-937b-27063820dc28"
Response
Report fetched successfully. Note: a 200 does not imply the verification is finished — inspect data.status and each check's status/result.

