Dashboard

Developer Overview

VerifyHuman provides APIs, webhooks, widgets, and hosted flows for teams that need more control than no-code VerifyFlow. This page explains the full integration surface available to developers.

Architecture overview

VerifyHuman has two layers:

VerifyFlow (no-code layer) : Business users use VerifyFlow to launch hosted verification pages without writing code. VerifyFlow is built on top of the same verification engines and hosted page infrastructure described below.

Verification engines (developer/API layer) : Developers can access the underlying engines directly through REST APIs, widgets, webhooks, and hosted pages. These power both VerifyFlow and custom integrations.

You do not need to use both layers. VerifyFlow is the fastest path to launch; direct API access gives you the most control.

Verification engines

Each engine is available through its own API endpoint:

Engine API path What it verifies
VerifyHuman POST /api/verify Human presence — liveness and bot detection
VerifyAge POST /api/v1/verify-age/verify Age assurance — selfie-based age estimation
VerifyIdentity POST /api/identity/v1/submit Identity assurance — selfie + government ID
VerifyTrust POST /api/compliance/v1/screen Trust review — structured screening signals

All engines require an API key in the X-API-Key header (or the clientKey form field for the human presence endpoint).

→ Full API documentation
→ Authentication and API keys

Integration paths

REST API

Direct server-side or client-side API calls. Full control over request timing, error handling, and result processing.

Best for: embedded verification flows, server-side decisions, programmatic batch workflows.

→ Integration Guide

Embeddable widget

A JavaScript widget that you drop into any webpage. The user completes verification in-page without navigating away.

<script src="https://app.verifyhuman.io/widget.js"></script>
<div id="verifyhuman-widget"
     data-product="verifyhuman"
     data-api-key="vhk-your-key-here">
</div>

Best for: signup flows, checkout gates, inline trust checks.

→ Widget documentation

Hosted flows

Managed verification pages generated and hosted by VerifyHuman. You create a hosted page config, get a token-based URL, and share it. The page handles the UX, camera access, and result capture.

Best for: teams that want a hosted UX without a custom frontend, single-use verification links, email-based verification prompts.

→ Hosted flows documentation

Webhooks

VerifyHuman sends signed webhook events to your configured endpoint when verifications complete. Payloads are HMAC-SHA256 signed.

POST https://your-app.com/webhooks/verifyhuman
X-VerifyHuman-Signature: sha256=...
Content-Type: application/json

Best for: real-time result processing, triggering downstream workflows, audit logging.

→ Webhooks documentation

VerifyFlow (from code)

You can publish and manage VerifyFlow flows via API, retrieve result summaries, and receive webhook events from VerifyFlow-powered verifications. VerifyFlow uses the same API keys and webhook infrastructure as direct integrations.

→ VerifyFlow getting started

API keys and environments

Every API key belongs to an environment: live or test.

When you publish a VerifyFlow, both a live key and a test key are created automatically. For direct API integrations, create keys from the dashboard under API Keys.

→ Test and live environments

Result objects

Every verification returns a structured JSON result object. The shape varies by engine. Key fields:

Field Meaning
verified / status The core pass/fail outcome
confidence Confidence level (0–99.9)
verification_id Unique ID for this verification
test_mode true if this was a test verification

→ Full result object reference
→ Result outcomes and delivery

Rate limits and error handling

All API endpoints return standard HTTP status codes:

Rate limits are enforced per API key. Contact support for limit details specific to your plan.

→ Troubleshooting

SDKs and mobile

Need help?