Skip to main content

Documentation Index

Fetch the complete documentation index at: https://truv.com/docs/llms.txt

Use this file to discover all available pages before exploring further.

When testing Document Processing, use the sample PDFs below. Upload these documents to test successful parsing, various tax form types, and suspicious document detection.
Test scenarios use the file name to determine results. The sandbox ignores actual file contents. Only the file name matters.
Trigger a suspicious result on any doc upload test scenario. Add the prefix suspicious. to any test file name from this page (for example, rename most.recent.paystub.pdf to suspicious.most.recent.paystub.pdf) and upload it. The doc upload task will return data with is_suspicious: true. This works for every test file listed below — paystubs and tax forms.

​
Pay stubs

DocumentDownload
Most recent paystubmost.recent.paystub.pdf
Next recent paystubnext.recent.paystub.pdf
First paystubfirst.paystub.pdf

​
Tax documents

DocumentDownload
W-2w2.pdf
1099-DIV1099div.pdf
1099-G1099g.pdf
1099-INT1099int.pdf
1099-MISC1099misc.pdf
1099-NEC1099nec.pdf
1099-R1099r.pdf
SSA-1099ssa1099.pdf
1040f1040.pdf
For 1099 tax documents, Truv supports parsing formats from any year after 2021. This includes 1099-DIV, 1099-G, 1099-INT, 1099-MISC, 1099-NEC, and 1099-R.

​
Volunteer documents

DocumentDownload
Volunteer lettervolunteer_letter.pdf
Volunteer timesheetvolunteer_timesheet.pdf

​
Suspicious document detection

ScenarioDescriptionDownloads
Tampered documentsInformation is falsified or manipulatedTampered 1, Tampered 2, Tampered 3
Different SSNsPersonal information is inconsistent across documentsSSN 1, SSN 2, SSN 3
Different applicant namesPersonal information is inconsistent across documentsApplicant 1, Applicant 2, Applicant 3
No data or invalid dataInformation is missing or unable to be parsedNo data 1, No data 2, No data 3
To flag any doc upload test scenario as suspicious, rename the file with the suspicious. prefix before uploading. See the tip at the top of this page for the full rule and examples.

​
Validation failures

Use these files to test the file-level validation flags returned by the Document Collections API. Each file triggers a specific validation failure on the collection retrieve response. In the sandbox, only the file name determines the test scenario — the actual file contents are ignored. You can upload any PDF as long as the filename matches.
DocumentTriggersDownload
Duplicate fileis_unique: false — upload any file twice in the same collection, or use the provided fileduplicate.pdf
Unreadable fileis_readable: falseunreadable.pdf
Password-protected fileis_accessible: false (password: paystub123)password.pdf
Unsupported MIME typeis_supported_type: falseunsupported_type.pdf
Processing failurestatus: failed after validation passesfailed.pdf

​
Base64 encoding for Document Collections API

The Document Collections API accepts base64-encoded file content when creating or uploading to a collection. To encode a test document for use with the API: 
# Download a test document
curl -O https://citadelid-resources.s3.us-west-2.amazonaws.com/doc_upload/most.recent.paystub.pdf

# Base64 encode it
base64 -i most.recent.paystub.pdf -o most.recent.paystub.b64

# Use the encoded content in your API call
cat most.recent.paystub.b64
Pass the base64 string as the content field when creating a document collection: 
{
  "files": [
    {
      "filename": "most.recent.paystub.pdf",
      "content": "BASE64_ENCODED_CONTENT"
    }
  ]
}
In sandbox mode, the file name determines the test scenario, not the actual content. The base64 content can be from any valid PDF — only the filename matters for sandbox behavior.