Skip to main content

Overview

Cases in Veridox provide a structured way to organise document verification workflows. Each case acts as a container for related documents that need to be analysed together, enabling efficient tracking, audit trails, and compliance reporting.

What is a Case?

A case represents a single verification workflow that groups related documents. Common examples include:
  • Customer onboarding: Identity documents, proof of address, employment verification
  • Insurance claims: Damage photos, repair estimates, supporting documentation
  • Loan applications: Bank statements, payslips, proof of residence
  • Compliance checks: Corporate documents, director IDs, company registration
Case Benefits: Cases enable batch processing of documents, maintain audit trails, and support compliance reporting requirements.

Case Lifecycle

1

Creation

Create a case with a descriptive label and optional file placeholders
2

File Upload

Upload documents to the case using pre-signed URLs
3

Locking

Case automatically locks when files start uploading to ensure complete batch analysis
4

Analysis

All files in the case are analysed in parallel
5

Completion

Case reaches completed state when all file analyses finish

Creating Cases

With File Placeholders

Create a case and pre-define expected files to receive upload URLs immediately:
Response:

Without File Placeholders

Create an empty case and add files later:

Adding Files to Cases

Upload to Pre-signed URLs

After creating a case with file placeholders, upload files directly to storage:

Adding Additional Files

Add files to an existing unlocked case:
Case Locking: Once you start uploading files to a case, it becomes locked and you cannot add more files. Upload all documents in a single batch to avoid this limitation.

Retrieving Cases

List All Cases

Get a paginated list of all cases belonging to you:

Pagination Parameters

Response:
Pagination Best Practice: The API returns a maximum of 100 cases per request. For large datasets, implement pagination by incrementing the offset parameter by limit on each request.

Get Case Details

Retrieve comprehensive information about a specific case:
Response:

Monitoring Progress

Real-time with Server-Sent Events (SSE)

Monitor case analysis progress in real-time:

Polling for Updates

Alternative progress monitoring using HTTP polling:

Case Status Values

File Analysis Status

Individual File Status

Case Labelling Best Practices

Use descriptive, meaningful labels for easy identification and tracking:

Good Examples

Avoid

Use Cases and Patterns

Identity Verification (KYC)

Insurance Claims Processing

Loan Application Verification

Advanced Case Management

Batch Case Creation

Create multiple cases efficiently:

Case Search and Filtering

Filter cases by status or date:

Error Handling

Implement robust error handling for case operations:

Rate Limits

Case operations are subject to rate limiting to ensure system stability. For a complete list of limits across all endpoints, see the Rate Limiting Guide.

Best Practices

Organisation

Descriptive labels - Use meaningful identifiers for easy case tracking
Unique labels (case-insensitive) - Case labels must be unique per user, even if the only difference is letter casing
Consistent naming - Establish naming conventions across your organisation
Batch related documents - Group all related files in a single case

Performance

Pre-plan files - Create cases with file labels to get upload URLs immediately
Parallel uploads - Upload multiple files simultaneously for faster processing
Use SSE - Prefer Server-Sent Events over polling for real-time updates

Security

API key protection - Never expose API keys in client-side code
Upload URL expiration - Complete uploads within 1 hour (URL expiry time)
Access control - Only you can access your own case data
Audit trails - All case operations are logged for compliance

Error Handling

Retry logic - Implement exponential backoff for transient failures
Rate limit handling - Respect rate limits and implement appropriate delays
Upload validation - Verify file uploads completed successfully before proceeding

Common Issues

Case Already Locked

Problem: Cannot add more files to a case Solution: Cases lock when file uploads begin. Plan all required files upfront or create a new case for additional documents.

Upload URL Expired

Problem: Pre-signed upload URL no longer works Solution: URLs expire after 1 hour. Request fresh URLs if needed by creating a new case or using the additional files endpoint.

Analysis Timeout

Problem: Analysis takes longer than expected Solution: Large files (>10 MB) may take 3-5 minutes. Check case status periodically and contact support if analysis exceeds 10 minutes.

SSE Connection Drops

Problem: Real-time progress monitoring disconnects Solution: Corporate networks may block SSE. Implement automatic fallback to HTTP polling.

Create Case API

Detailed API reference for creating cases

List Cases API

Retrieve and filter cases

Document Analysis

Understanding forensic analysis results

Quickstart Guide

Complete workflow from case creation to results