Retrieve DocV Documents and Images
Download the document and selfie images captured during a Predictive DocV verification using the Evaluation API or the RiskOS™ Dashboard.
After an evaluation completes, you can retrieve the images the consumer captured — for your records, manual review, or compliance. Retrieve them programmatically through the Evaluation API, or view them in the RiskOS™ Dashboard.
Dashboard viewing:
To make images appear in the RiskOS™ case view, include the Socure Image Request enrichment step in your workflow. This step retrieves images and attaches them to the evaluation for reviewers.
Testing in Sandbox:
In Sandbox, add a WAIT (10s) step before the Socure Image Request enrichment so images finish processing before retrieval. See Test your integration for the full Sandbox workflow.
Retrieve documents via the API
Use the Download Evaluation Documents endpoint to retrieve a ZIP of images and case attachments for a given eval_id.
GET https://riskos.sandbox.socure.com/api/evaluation/{eval_id}/documentsGET https://riskos.socure.com/api/evaluation/{eval_id}/documents| Header | Required | Description |
|---|---|---|
Authorization | Yes | Bearer YOUR_API_KEY — use the correct key for your environment. |
X-API-Version | No | Pins a specific API version (for example, 2025-01-01.orion). |
curl --location --request GET \
'https://riskos.socure.com/api/evaluation/fb1ddadc-6dba-4ce4-aa6d-25c005b192b5/documents' \
--header 'Authorization: Bearer YOUR_API_KEY'A 200 OK returns an application/zip archive named {eval_id}_document.zip.
Retrieve images
The ZIP contains consumer-submitted images under user_uploaded/ and any reviewer-added files under case_attachments/:
user_uploaded/ # Consumer-submitted identity documents
├─ document_verification/
│ ├─ documentfrontDoc_Front_1_blob.jpg
│ └─ documentbackDoc_Back_1_blob.jpg
└─ vouched_id_verification/
└─ Doc_Selfie_1_blob.jpg
case_attachments/ # Attachments added via the RiskOS™ Dashboard
├─ identity.pdf
└─ additional_doc.pdf| Filename | Description |
|---|---|
documentfrontDoc_Front_1_blob.jpg | Front of the identity document |
documentbackDoc_Back_1_blob.jpg | Back of the identity document |
Doc_Selfie_1_blob.jpg | Selfie image |
Retention considerations
The endpoint returns 400 Bad Request with { "message": "No Documents Found" } when images are unavailable. This is expected in these cases — not an integration error:
| Scenario | Detail |
|---|---|
| Military IDs | Images are deleted immediately due to regulatory requirements. Identified by documentType.type = "Military". |
| Minors | Images are deleted immediately when the consumer is under 18. |
| Data retention | Images were removed after capture due to data-retention policies or deletion requests. |
Don't add error handling for the image step:
Avoid adding workflow error handling for the Socure Image Request enrichment. The scenarios above are expected, and the step returns errors by design when no images are available.
Security considerations
- Retrieved images and the
evaluation_completedpayload can contain PII. Protect them with access control, encryption at rest, and a retention policy. - Use the API key that matches your environment; a Production
eval_idis not accessible with a Sandbox key. 403 Forbiddenindicates the client lacks permission for the resource;404 Not Foundindicates the evaluation does not exist.
Related
Updated about 22 hours ago