> For the complete documentation index, see [llms.txt](https://doc.faceplugin.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.faceplugin.com/products/id-document-recognition-sdk/id-document-liveness-sdk.md).

# Liveness

Faceplugin ID Document Liveness SDK. On-premise document anti-spoofing HTTP API for Linux and Docker. Screen, print, and substitution attacks. No OCR. Port 8086.

### Overview

**Faceplugin ID Document Liveness SDK** checks whether the image is a **physical ID** or an attack: a screen replay, a printout, a digitally created page, or a substituted portrait.

This product does **not** read fields. OCR, MRZ (machine-readable zone), and barcodes are turned off. For **passport OCR plus authenticity** in one engine, use [ID Document Recognition](/products/id-document-recognition-sdk.md) with a Liveness-capable license. This is **not** face anti-spoofing — use [Face Liveness Detection](/products/face-recognition-sdk/liveness-detection-sdk.md) for selfies.

Today the public **SDK** is **Linux / Docker** (HTTP port **8086**). There is no public mobile SDK.

```mermaid
flowchart LR
  PageImage --> Authenticity
  Authenticity --> SecurityJSON
```

### Features

* [x] Document authenticity and liveness checks
* [x] Screen replay and digital-source detection
* [x] Printed copy checks
* [x] Front and back (multi-page) images
* [x] On-premise (your machine only)

### Platforms

<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td></td><td><strong>Server SDK</strong></td><td>Linux / Docker authenticity-only HTTP API on port 8086.</td><td><a href="/products/id-document-recognition-sdk/id-document-liveness-sdk/server-sdk.md">Server</a></td></tr></tbody></table>

### FAQ

**Does this read the MRZ?** No. Use ID Document Recognition for OCR / MRZ.

**How do I call it?** `POST /api/documentLiveness` after `POST /api/activate`. See [Linux SDK](/products/id-document-recognition-sdk/id-document-liveness-sdk/server-sdk/id-document-liveness-linux-sdk.md).

### Use cases

* **KYC authenticity gate** — reject screen replays and printouts before OCR (`POST /api/documentLiveness`, port **8086**)
* **Split architecture** — run authenticity-only on Linux while OCR runs in another service
* **Fraud prevention** — physical-ID checks without reading personal fields

### Related documentation

* [ID Document SDK](/products/id-document-recognition-sdk.md) · [Face SDK](/products/face-recognition-sdk.md) · [Glossary](/help/resources/glossary.md)
* [Document security check fields](/products/id-document-recognition-sdk/document-security-check-fields.md)
* [Request a License](/help/request-a-license-and-support.md) · [Try it](/getting-started/try-it.md)
* [Combining products (eKYC)](/getting-started/choose-a-product.md) · [SDK comparison](/help/comparisons.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://doc.faceplugin.com/products/id-document-recognition-sdk/id-document-liveness-sdk.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.