> For the complete documentation index, see [llms.txt](https://docs.zapsign.com.br/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zapsign.com.br/zapsign-api/english/signer-verification-details.md).
# Signer validations details
**GET** `https://api.zapsign.com.br/api/v1/signer-verification-details/{{signer_token}}/`
#### Headers
Name
Type
Description
Authorization*
string
apiToken ahead of the "Bearer" text.
Ex: Bearer c7f35c84-7893-4087-b4fb-d1f06c23
#### Params
Name
Type
Description
signer_token*
string
Unique token of the signer (obtained when creating the document).
#### Example response
The endpoint returns all attempts made by the signer, allowing you to track the validation history and understand possible failure reasons:
{% tabs %}
{% tab title="200 - Success" %}
```json
{
"token": "0abe0677-72d7-4816-9ba8-317145d387ea",
"selfie_validation_type": "identity-verification-global",
"validations": [
{
"type": "Identity verification",
"validation_number": "cd461e6a-a5d5-4bd7-8e50-20263c9f64a9",
"status": "success",
"reason": "",
"created_at": "2025-06-05T18:51:26.286366Z",
"document_photo_url": "https://zapsign.s3.amazonaws.com",
"document_verse_photo_url": "https://zapsign.s3.amazonaws.com/",
"selfie_photo_url": "",
"document_ocr": {
"process_id": "cd461e6a-a5d5-4bd7-8e50-20263c9f64a9",
"name": "MARIA",
"last_name": "SOUZA",
"document_type": "ID_CARD",
"document_number": "11111111",
"date_of_birth": "1980-01-01",
"document_country": "BR"
}
},
{
"type": "Name validation",
"status": "success",
"reason": "",
"created_at": "2025-06-05T18:51:26.286366Z"
}
]
}
```
{% endtab %}
{% tab title="404 - Not found" %}
```json
{
"error": "Signer has attempts"
}
```
{% endtab %}
{% endtabs %}
### About the validation result
This endpoint allows you to check the **result of the validation process** defined in the `selfie_validation_type` parameter. Each type of validation has **specific steps** that verify different aspects of the document and/or the signer’s face.
Within each step, there are **sub-validations**, and for each of them the endpoint response returns:
* The **status** (success or failure).
* The **reason** field, which explains the failure reason, when applicable.
Below are the different types of validation available and their corresponding steps:
***
**liveness-document-match**
This method performs **two main validations**:
* **Document recognition**: checks if the uploaded front photo of the document really corresponds to an identity document and if it contains a photo.
> Important: it does not apply advanced fraud models nor detect “photo of a photo” cases.
* **Face match**: compares the passive video of the signer’s face with the document photo, ensuring it is the same person. The result includes the URL of the captured face photo.
***
**face-match-and-datavalid**
Available only for **Brazil – CNH**. This method performs **a single validation**:
* Compares the **name and CPF** with **Serpro** databases, and checks whether they match the person identified in the passive video recorded during signing.
***
**identity-verification-global**
This method performs **three complementary validations**:
* **Identity verification**: checks if the document is real using fraud detection models and returns the data automatically extracted (OCR), including:
* `name`
* `last_name`
* `document_type`
* `document_number`
* `date_of_birth`
* `document_country`
* **Name validation**: compares the name extracted from the document with the name provided by the signer. The validation is considered approved if the similarity is **greater than 75%**.
* **CPF validation (Brazil)**: when the document is from Brazil and contains a CPF, an automatic check is performed with the Federal Revenue database.
***
**identity-verification**
Available for **Colombia, Mexico, Chile, and Peru**. This method performs **two validations**:
* **Identity verification**: checks that the document is real using fraud detection models, queries government databases, and ensures the passive video corresponds to the same person in the document.
* **Name validation**: compares the name extracted from the document with the name provided by the signer, applying the same similarity logic as in the *identity-verification-global* method.
---
# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.zapsign.com.br/zapsign-api/english/signer-verification-details.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.