Verification APIs

Embed verification checks into your workflow.

Connect eligible Nilinde checks to onboarding, lending, mobility or internal screening processes through controlled API access and structured responses.

Request API Access Discuss Integration Requirements

API DELIVERY FLOWSandbox available

CLIENT WORKFLOWNILINDE VERIFICATIONSTRUCTURED RESULT

01Verification requestRequired data acceptedReceived

02Supported checkConfigured service processedComplete

03Structured responseStatus and reference returnedDelivered

04Exception routeEscalation where configuredAvailable

Controlled access · Scoped checks · Traceable responses

01BEST FORDigital platforms, fintechs, mobility operators and high-volume teams.

02USE WHENVerification needs to sit inside an existing onboarding or operating workflow.

03ACCESS THROUGHApproved credentials, sandbox testing and controlled production access.

Eligible verification services

Connect the checks your workflow requires.

Available services are confirmed during scoping according to a use case, authorised source, expected volume and applicable requirements.

Access is use-case specific.A listed service is not a guarantee of universal access. Nilinde confirms availability, lawful purpose, data requirements and applicable source conditions before activation.

National IDIdentity verification for supported customer and subject records.

Driving LicenceLicence verification for driver and mobility onboarding.

PSV BadgePSV-status confirmation where the service is enabled.

KRA PINTax-identifier verification for relevant workflows.

Police ClearanceClearance verification through the supported route.

Phone NumberContact-number verification where included.

Social Media ScreeningConfigured screening where supported and appropriate to the use case.

Integration journey

Move from use case to controlled production access.

Technical access follows agreed business purpose, checks, data requirements and operating environment

01
Confirm use caseDefine the decision, checks, users and expected volumes
02
Approve accessConfirm data fields, purpose and technical requirements
03
Issue sandboxProvide controlled credentials for integration testing
04
Test workflowValidate requests, responses, errors and status handling
05
Enable productionActivate agreed services after technical validation

Operational controls

Designed for predictable verification requests

The API route is structured around scoped access, consistent request handling and traceable verification responses

Scoped credentialsAccess is limited to services enabled for a client

Controlled data fieldsOnly information required by configured check is accepted

Structured responsesSupported checks return consistent status and result fields

Error handlingInvalid, incomplete or unavailable requests return defined outcomes

Status notificationsWebhook or status handling can be configured where enabled

Escalation routeHuman review supports exceptions or non-automated checks

API responses support a client’s workflow and decision-making. A client remains responsible for lawful collection, appropriate use, access controls and any final decision made from a result.

Request access

Connect verification where a decision is already happening.

Tell us the checks required, expected volumes, operating environment and how results should return to your workflow

Request API Access