Verifisha API · v1

Verify anyone.
In one request.

Identity, KYB, credit, employment and AML checks behind a single API — with consent built into the report lifecycle.

Verifisha — KYC, KYB and background checks
Built for AI-assisted builds

Let your assistant read the contract, not remember it.

Every page is published as machine-readable llms.txt, and the quickstart ships prompts you can paste straight into Claude, Cursor, Copilot or ChatGPT. They point the model at the live docs, so it writes against today's API instead of a version it half-remembers.

paste into your assistant
Read https://docs.verifisha.com/llms.txt
before answering.

Write a service that creates a Verifisha
report and handles the report.ready webhook.
My stack is <language and framework>.

Request to result

You make one call. We make the next one.

Create the report, then wait. When every check has finished, Verifisha posts the whole thing to your endpoint — outcome, risk and evidence. No polling loop to write.

01

You create a report

A subject and the checks you want, in one call.

POST /api/v1/reports
02

Verifisha runs the checks

Each check runs and its evidence is recorded against the report.

status: PROCESSING
03

The result arrives

A signed delivery carrying every outcome, risk and flag.

COMPLETED · LOW
your request
POST /api/v1/reports
Authorization: Bearer vrf_test_...
Idempotency-Key: case-1042

{
  "reports": [{
    "subject": {
      "subjectType": "INDIVIDUAL",
      "fullName": "Jane Doe",
      "idNumber": "36901234"
    },
    "checksRequested": [
      "IDENTITY", "KRA_PIN", "METROPOL_SUMMARY_CRB_REPORT"
    ],
    "purpose": "Employment screening",
    "consent": { "mode": "CUSTOMER_ATTESTED",
                 "obtained": true }
  }]
}
our webhook
POST https://example.com/hooks/verifisha
X-Verifisha-Event: report.ready
X-Verifisha-Signature: ...

{
  "lifecycle": { "event": "report.ready",
                 "terminal": true },
  "report": {
    "status": "COMPLETED",
    "riskLevel": "LOW",
    "compositeScore": 10,
    "conclusion": { "title": "Clear" }
  },
  "checks": [{
    "name": "IDENTITY",
    "status": "COMPLETED",
    "riskLevel": "LOW",
    "flags": []
  }]
}

Built for integrators

The details that decide how your week goes.

500 reports, one request

Bulk by default — the same call creates one report or hundreds.

One host, both environments

Going live is a change of key, not a change of URL.

Safe retries

An Idempotency-Key means a timeout you retry cannot bill twice.

Signed, versioned deliveries

Every webhook carries a signature, an environment and a schema version.

One pagination envelope

Every list returns items with hasNext. Loop until it is false.

Errors you can branch on

RFC 7807 problem+json with a stable errorCode on every failure.

Build against sandbox today. Go live with the same code.

A vrf_test_ key never runs a billable check. When you are ready, swap in the live key — the host does not change.