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.

What the API does
Six things, one key.
Run checks
Identity, tax, credit, employment and business checks. Name the checks you want on a report and Verifisha returns the results with their evidence.
POST /api/v1/reportsWebhooks
Signed deliveries when a report reaches a terminal state, carrying every check's outcome, risk and evidence. Most integrations never read a report back.
report.readyConsent, your way
Already have your customer's approval? Attest to it and the checks run immediately. Or let Verifisha collect it through a hosted link.
consent.modeRecurring checks
Re-run a check stack on a cadence and raise an alert when a result changes. Alerts reach you by webhook too.
POST /api/v1/monitoringReference questionnaires
Send a referee a questionnaire attached to a report. They answer without a Verifisha account, and the responses land on the report.
POST /api/v1/reports/{id}/referencesThe check catalogue
Read which checks your workspace can run, what each needs and what it returns. Activated and retired without an API version change.
GET /api/v1/checks/definitionsLet 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.
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.
You create a report
A subject and the checks you want, in one call.
POST /api/v1/reportsVerifisha runs the checks
Each check runs and its evidence is recorded against the report.
status: PROCESSINGThe result arrives
A signed delivery carrying every outcome, risk and flag.
COMPLETED · LOWPOST /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 }
}]
}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.