List verifications

GET /api/kyc/verifications

Your organisation’s verification history, paginated and filterable — reconcile your records without keeping your own ledger of ids. Scoped to the key’s environment, so a sandbox key never lists production traffic.

Records you have deleted are not listed and are not counted in total.

Authentication: Authorization: Bearer sk_… (secret key required), like the per-id result read beside it.

Query parameters

Response

{
  "verifications": [
    {
      "verificationId": "cmt…",
      "requestId": "order_1001",
      "externalUserId": "user_42",
      "metadata": { "loanId": "loan_20191" },
      "channel": "sdk",
      "subjectType": "individual",
      "status": "approved",
      "checkStatus": "verified",
      "reasonCode": null,
      "country": "NG",
      "idType": "bvn",
      "workflowId": "wf_AbC123dEf456",
      "workflowVersion": 3,
      "createdAt": "2026-08-20T12:00:00.000Z",
      "completedAt": "2026-08-20T12:00:04.512Z"
    }
  ],
  "total": 812,
  "page": 1,
  "pageSize": 25
}

Rows are deliberately light: identifiers and states, no biodata. metadata is your own customer metadata echoed unchanged, not something Toden derived. status is the outcome to act on (what the checks, your workflow or a reviewer concluded); checkStatus is what the automated checks themselves found, so approving a failed check (an exception) stays distinguishable from approving a passing one. See Status and checkStatus. The full result, PII included, lives on GET /verifications/:id.

Business rows additionally carry businessName.