D8N— trust infrastructure for human connection. Home
ContactBuild on D8N
DEVELOPERSEarly access

Trust and connection, as an API.

You already have a product, members and a brand. What you should not have to build is the trust layer. Call D8N for the parts that punish amateurs — liveness and face match, AI-generated and stolen photo detection, romance-scam risk on messages — and keep everything that makes your product yours.

Request API accessWhat the API covers
illustrative
POST /v1/verify/sessions
{
  "member_id": "mem_8f2k1",
  "checks": ["liveness", "face_match", "document"],
  "brand": "your-brand"
}

→ 201 Created
{
  "session_id": "vs_31ac9",
  "status": "pending",
  "url": "https://verify.d8n.tech/s/vs_31ac9"
}

REST API

Versioned endpoints for every live module.

Webhooks

Every D8N event delivered to your servers.

Sandbox

Test verifications and scam checks with fake data.

Web and mobile SDKs

Drop-in verification and chat screens.

One event vocabulary across D8N

member.createdprofile.publishedverification.completedmatch.createdmessage.sentreport.createdenforcement.appliedsubscription.started
Request API accessWhat the API covers
QUESTIONS

Straight answers

Integration questions are best answered against your actual product — tell us what you have and we will tell you what changes.

Can I use the D8N API without white-labelling the platform?

Yes. The API is the path for products that already exist. You keep your product, your data model and your apps, and call D8N for the capabilities you do not want to build — most commonly identity verification, AI-fake photo detection and scam risk on messages.

Is the API generally available?

It is in early access. The endpoints are the ones D8N's own brands run on, and access is granted per integration so the contract can be held stable for each partner while it stabilises publicly.

How do I find out about a verification result?

Two ways: the verification session resource can be read directly, and a verification.completed webhook is delivered to your endpoint with the assurance level and the resulting mark. Webhooks are the recommended path — polling a session is a fallback, not a design.

What happens if D8N flags one of my members?

You decide. A risk assessment comes back with a state, the reasons behind it, and a recommended action — warn, challenge, restrict. D8N never silently acts inside your product; your product applies the action it chooses.