Free demo hits. Pay when you go live. Request access
Documents & Biometrics

Deepfake Detection API

Analyse a selfie or short video for generative artefacts, face swaps and replay attacks and return a risk score, so liveness checks are not fooled by AI-generated media.

Response
Real-time
Inputs
1 required · 1 optional
Consent
Not required
Billing
Per successful call
POST /v1/deepfake-detection
Sandbox · Production
  1. Your application sends

    • Selfie image or video*
    • Risk threshold (0–100)
  2. emver API

    Validates the request, queries the source, normalises the answer and logs the call. Billed only on success.

  3. Verified with

    Authoritative source

  4. You receive

    • Deepfake detected
    • Risk score
    • Attack signals detected
deepfake-detection Full reference
Overview

What the Deepfake Detection API does

Send a selfie image or a short video clip. The API returns a deepfake probability, the attack types detected (face swap, synthetic generation, screen replay) and a pass or fail against your threshold.

Benefits

Why teams use the Deepfake Detection API

Flag synthetic or manipulated faces in selfies and video frames.

Closes the AI gap

Liveness alone no longer stops generated faces; this does.

Drops into existing flows

Same media you already capture for Face Match and Liveness.

Use cases

Where it's called

Where the Deepfake Detection API is typically called, and what it settles there.

Video KYC and selfie onboarding

Reject synthetic faces before an agent ever sees them.

Account recovery

Protect high-value resets from impersonation.

How it works

Four steps, one response envelope

Request and response details, environments and a ready-to-import collection are in the developer console.

  1. 01

    Authenticate

    Call with your organisation API key. Sandbox and production use the same contract.

  2. 02

    Send the inputs

    Selfie image or video as a JSON body. Optional fields sharpen the match.

  3. 03

    We verify at source

    emver queries the authoritative record, normalises the answer and logs the request.

  4. 04

    Act on the result

    A verification status plus the fields listed above, in the same response envelope as every other API.

Privacy and security built in

Consent recorded · Payloads not retained beyond your retention window · Every request traceable

FAQ

Deepfake Detection API: frequently asked questions

What teams ask before adding the Deepfake Detection API to their integration.

No. Liveness proves a real person is present; deepfake detection proves the face is not synthetic. Run both for high-risk journeys.

Related

APIs that run alongside it

Usually called with the Deepfake Detection API, on the same key.

All APIs
Access usually set up within one working day

Start verifying with emver today.

Tell us which APIs and what monthly volume. We set up your organisation, approve the APIs with demo hits and share per-call pricing.