Which RPT reports the API produces today, and which are planned.
A TrustVerify-branded PDF is a compliance artefact, so the API only issues one for a report type that has a real renderer and whose subject matches the check it is rendered from. Four report types are produced as PDFs today — RPT-001, RPT-002, RPT-003 and RPT-KYA — plus RPT-016, which is the ZIP evidence bundle rather than a PDF.
Request a report by passing "generateReport": true in any check call, or fetch it later via /reports/{reportType}/{checkId}.pdf. Reports are retained for 7 years by default.
The remaining codes are planned, not shipped. Asking for one returns 501 NOT_IMPLEMENTED listing the types that are supported; asking for a supported type against the wrong kind of check returns 409 with the correct type named. Neither case ever produces a placeholder document.
| Report | Name | Produced from | Status |
|---|---|---|---|
| RPT-001 | Individual KYC | kyc checks | Live — PDF |
| RPT-002 | Business KYB | kyb checks | Live — PDF |
| RPT-003 | AML Screening | aml_screen checks | Live — PDF |
| RPT-KYA | Know Your Agent | kya checks | Live — PDF |
| RPT-016 | Regulatory Evidence Bundle | any check with a supported report | Live — ZIP, hashes only (not signed) |
| RPT-004 | Enhanced Due Diligence | — | Planned — returns 501 |
| RPT-005 | Address Verification | — | Planned — returns 501 |
| RPT-006 | Device & IP Fraud | — | Planned — returns 501 |
| RPT-007 | Liveness Check | — | Planned — returns 501 |
| RPT-008 | SAR | — | Planned — returns 501 |
| RPT-009 | Right to Rent / Right to Work | — | Planned — returns 501 |
| RPT-010 | Escrow Transaction | escrow transactions (dashboard only) | Not on the public API — 501 |
| RPT-011 | Document Authenticity | — | Planned — returns 501 |
| RPT-012 | Ongoing Monitoring | — | Planned — returns 501 |
| RPT-013 | Risk Score Summary | — | Planned — returns 501 |
| RPT-014 | UBO Mapping | — | Planned — returns 501 |
| RPT-015 | Compliance Audit Log | — | Planned — returns 501 |
Planned types have no renderer and no release date. Do not build a compliance process that depends on one — GET /api/v1/reports/{type}/{checkId} is the authoritative answer, and it will tell you plainly.