Skip to content

Document uploads and evidence

Dockt accepts a file, classifies what the file represents, and extracts public facts from it. In an Assessment, Dockt then decides whether that Document supports one of the worker’s evidence requirements.

These are separate questions:

  • classified_as describes the uploaded file.
  • facts contains values Dockt read from that file.
  • accepted_evidence_types describes the purpose of evidence required by an Assessment.
  • Requirement Document ID arrays show whether an uploaded Document actually supports that requirement.

Use classified_as to interpret the uploaded file. Use the Assessment’s requirements to determine whether that file satisfies an evidence need.

Upload one non-empty file no larger than 10 MB. Dockt accepts these file formats:

FormatCommon media type
PDFapplication/pdf
JPEGimage/jpeg
PNGimage/png
GIFimage/gif
WebPimage/webp

Declare the media type when possible. If the upload uses application/octet-stream or omits a useful media type, Dockt inspects the file signature for these formats.

After classification, use the classified_as fields as follows:

  • family groups related documents for display and reporting.
  • type identifies the supported document behavior Dockt applied.
  • variant distinguishes a document form when Dockt returns one. It can be null.

Treat all three values as open strings. Handle an unfamiliar future value without rejecting the entire Document response.

A fact appears only when Dockt exposes a value from that file. A missing fact key does not, by itself, mean the Document is invalid.

Use:

  1. status to determine whether processing is complete.
  2. document_result for the top-level Document conclusion.
  3. issues, fraud_signals, and findings for actionable reasons.
  4. facts, verifications, enrichment, and credential_assertions for supporting detail.

The Facts and credential assertions reference lists every public fact and check code.

Social compliance package entries list possible evidence types before Dockt evaluates a specific worker. Read them with GET /v1/social-compliance-packages.

After you create an Assessment, use its requirements as the case-specific source of truth:

  • Show label and reason to explain what is needed.
  • Treat accepted_evidence_types as machine-readable evidence-purpose codes.
  • Upload the file without assigning it to a requirement.
  • After processing, use supporting_document_ids, pending_document_ids, review_document_ids, and invalid_document_ids to see how Dockt evaluated it.

Use the returned requirements as the checklist for that worker. Requirements depend on the worker context and the social compliance packages enabled for the Workspace.

If Dockt can read the file but cannot match a supported document type, the Document completes with:

  • status: "completed"
  • document_result: "review_required"
  • An issue with code: "type_unknown"

This is a completed review outcome, not a processing failure. Ask for a supported document or route the file to a person for review.