Skip to main content
Didit lets you export verification data in two formats - PDF for individual session reports and CSV for bulk data exports. Both options are available from the Didit Console and through the API.

Export PDF

Generate a PDF report containing the full verification results of an individual session. You can do this in two ways:
  • From the Console - open any session and click the Download PDF button.
  • Via the API - call the Generate PDF endpoint.
Export PDF from the verification dashboard
The PDF includes all verification steps, extracted data, biometric scores, AML results, and the final decision - formatted for compliance audits and regulatory filings.

Full user history PDF

To get every session for one user in a single file, you can do this in two ways:
  • From the Console - open that user’s detail page and use Actions → Download PDF.
  • Via the API - call the Download user history PDF endpoint (GET /v3/users/{vendor_data}/generate-pdf/) with your API key. It returns the same document, so you can schedule periodic compliance exports or pull a user’s history into your own back office.
The report bundles a cover page (profile summary, feature status, session index) with the full standard report of every completed session sharing that user’s vendor_data, merged in chronological order. Only sessions in a reportable status (Approved, Declined, In Review, Kyc Expired) are included, capped at the 20 most recent. The cover page states when older sessions were left out.

Export CSV

The CSV export allows you to download verification session data in bulk for further analysis or record-keeping. Customize the exported data by selecting specific columns and filtering sessions.
Export CSV with column selection
Use CSV exports for periodic compliance reports, internal analytics, or importing verification data into your own systems.

The Reports page

Open Reports in the sidebar to see every export your organization has requested. The page lists CSV exports of your verifications, transactions, people and businesses.
  • Select New report to request an export, then pick the data and the filters.
  • A report generates in the background. Its status moves from Pending to Processing to Ready, or to Failed if it could not be built.
  • Download a report once its status is Ready.
  • Filter the list by Type or Status, or search by report ID or requester.
Members with reader access can view and download ready reports, but creating a new export needs an admin.

Retry failed export items

Didit reports individual failures in a verification CSV export through failed_item_ids (live session UUIDs) and failed_count (the length of that list). A READY export can contain successful records and failed items, so inspect these fields before treating it as complete. Deleted sessions are excluded and cannot be re-exported. Use List async reports to find an export, then Retrieve async report for its current failure list. These async export jobs are separate from the Regulatory Reports API. To retry selected failures, send item_ids with 1 to 1000 UUIDs from that report’s failure list. The report must be a READY or FAILED SESSION_EXPORT. Only its original requester can retry a subset, with read and write access to the exported resources. An API key or application token without that matching user identity receives 403; using the same application alone is not enough.
Replace the example UUID with an ID from failed_item_ids. Do not send date_from or date_to with this selection. The first request returns a new report with 201; replaying the same selected set returns that retry report with 200. A selection that overlaps an existing retry but does not match it returns 400. The original report stays unchanged. Omitting item_ids reruns the original export, optionally with both date_from and date_to in order. It does not automatically select failures. A report created by a failed-item retry requires an explicit selection for another retry.
Last modified on November 14, 2026