Introduction

Verifisha runs identity, tax, credit, employment, business and AML checks against Kenyan data sources. Every customer-facing API is routed through the gateway under /api/v1.

Reports are the execution boundary

There is no per-provider endpoint. You will not find /metropol or /kra here.

You create a report with a subject and a list of check names, and Verifisha calls the configured provider internally. Selecting CRB_STANDARD is how you call Metropol. Providers can be swapped or re-priced without your integration changing.

Quickstart

Create an API key, build against sandbox, then go live.

Consent

Let Verifisha ask the subject, or attest consent you already hold.

Payments

Your workspace pays, the subject pays, or someone else does.

API reference

Every customer operation, with an interactive playground.

What the API covers

Area	What it does
Checks	Discover checks, their prices and required inputs before you commit.
Reports	Where checks run. Create up to 500 at once, launch drafts, read results.
References	Send referees a questionnaire attached to a report.
Monitoring	Re-run checks on a schedule, with alerts when something changes.
Webhooks	Event delivery, so you do not have to poll.

Hosts

Environment	Base URL	Keys
Sandbox	`https://sandbox-api.verifisha.com`	`vrf_test_...`
Production	`https://api.verifisha.com`	`vrf_live_...`

All paths begin with /api/v1. See environments for what sandbox covers.