You already have a product, members and a brand. What you do not want to build is the trust layer — liveness checks, AI-generated photo detection, scam classifiers, enforcement, ban evasion — or the payment orchestration underneath it. That is what the D8N API is for.
Every live module has versioned REST endpoints. The ones customers reach for first are the ones that are hardest to build alone.
Every state change in D8N is delivered to your servers as a webhook using the same vocabulary across every module and every brand — member.created, verification.completed, match.created, message.sent, report.created, enforcement.applied, subscription.started. One shape to integrate against, not one per feature.
Verifications and scam checks are testable against fake data in a sandbox, so you can build and prove the unhappy paths — a held photo, an elevated risk state, a declined payment — before a real member ever meets them.
Identity verification and chat are the two surfaces where a rough implementation costs you completion rate. Drop-in web and mobile SDK screens are available for both, and they are the same screens D8N's own brands use.
If the answer you need isn’t here, ask us directly — we will tell you plainly when D8N is not the right fit.
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.
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.
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.
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.