Skip to main content
Zenoo is a verification orchestration platform. It connects your system to identity, screening, and company registry providers through a single API. You send data, Zenoo runs the checks, and you get structured compliance results back. What Zenoo does:
  • Company Verification — Company registry verification, director and UBO screening, corporate structure analysis
  • Person Verification — Document verification, biometric liveness, face matching, database checks
  • AML Screening — PEP, sanctions, adverse media, and watchlist screening via WorldCheck
You submit entity data over a REST API. Zenoo routes it to the appropriate providers, normalizes the results, scores risk, and returns a compliance report. No direct provider integrations required on your end.

​
Architecture

​
Processing pipeline

When you submit entity data, Zenoo runs through these stages:
1

Data ingestion

Your payload is validated and a case is created. If you included an external_reference that already exists, the existing case is returned instead.
2

Screening

The entity (and any associated individuals like directors or UBOs) is screened against WorldCheck databases for PEP status, sanctions list matches, adverse media, and watchlist entries.
3

Registry verification

For companies, Zenoo queries official company registries to verify legal name, registration number, company status, registered address, directors, and shareholders.
4

Document verification

For Person Verification flows that require user interaction, the individual captures identity documents and a selfie. Zenoo runs OCR, tamper detection, and biometric liveness checks.
5

Risk model evaluation

All check results feed into a risk scoring model that evaluates entity risk, geographic risk, industry risk, and screening risk. The output is a risk tier (Low, Medium, High) and a numeric score.
6

Alert generation

If screening returns hits, data mismatches are detected, or risk thresholds are exceeded, alerts are created for compliance review.
7

UBO discovery

For company verifications, Zenoo identifies beneficial owners from registry data and screens them individually.
8

AI research (optional)

Automated research on the entity using public data sources. Produces a structured summary of the entity’s background, industry presence, and risk indicators.

​
Processing timeline

StageTypical duration
API gateway routing< 1 second
WorldCheck screening3-10 seconds
Company registry lookup5-15 seconds
Document verification10-30 seconds (after user submits)
Biometric liveness5-15 seconds (after user submits)
Risk model evaluation1-5 seconds
Case creation and alert generation5-15 seconds
Auto-execute queued checks10-30 seconds
AI research30-120 seconds
For fully automated flows (Company Verification, screening), expect 2-5 minutes end to end. Flows that require user interaction (Person Verification document capture) add human time on top. Once the user submits, server-side processing completes in 30-60 seconds.

​
Two execution models

Zenoo supports synchronous and asynchronous execution.
Endpoint: POST /api with X-SYNC-TIMEOUTYour request blocks until checks complete or the timeout is reached. Results are returned directly in the HTTP response. Best for server-to-server flows like screening and Company Verification.
POST /api/gateway/execute/{project_hash}/api
Header: X-SYNC-TIMEOUT: 30000
Most integrations use both: sync for automated Company Verification and screening, async for interactive Person Verification flows.
  • Base URL (production): https://instance.prod.onboardapp.io
  • Base URL (staging): https://instance.staging.onboardapp.io
  • Auth header: X-API-KEY: your-api-key
  • Gateway pattern: POST /api/gateway/execute/{project_hash}/{action}

​
What’s next

Authentication

API keys, webhook signatures, security practices

Environments

Base URLs, endpoint reference, environment separation

First API Call

Working curl/Node.js/Python examples you can run in 2 minutes

Security Best Practices

Secure your integration against common vulnerabilities