> 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/create-check.md).

# Creating a Background Check

If you are integrating background checks through the ZapSign API, we recommend following this flow for proper implementation and the best user experience:

### 1. Create a [Person](/zapsign-api/english/create-check/person_check.md) or [Company](/zapsign-api/english/create-check/company_check.md) Check

The first step is to make a request to our **check creation endpoint**.\
Once submitted, the check enters the verification process.

{% hint style="warning" %}
**Estimated processing time:** between 2 minutes and 2 hours, depending on the databases consulted and the country.
{% endhint %}

***

### 2. Use the [Webhook for Results](/zapsign-api/english/webhooks/eventos/checks.md)

We recommend configuring a webhook to automatically receive a notification when the check is completed.

* Once the check is finished, ZapSign will send an **HTTP POST** notification to the webhook configured by your system, indicating that the results are ready to be retrieved.
* This avoids the need for repetitive polling requests to the server.

***

### 3. Retrieve the Results

Once you’ve received the webhook notification—or after the estimated processing time—you can obtain the results through our endpoints:

* [**Check Details**](/zapsign-api/english/check-detail.md)**:** This endpoint returns the complete **JSON** with all the information found, including:
  * The global score
  * Details by dataset
  * Severity levels associated with each finding
* [**Retrieve check**](/zapsign-api/english/check-status.md)**:** If you need a readable and shareable version, you can download the **PDF** of the check.

{% hint style="success" %}
💡 **Tip:** Using the webhook along with the result endpoints ensures an efficient and automated flow, avoiding unnecessary delays or redundant API calls.
{% endhint %}


---

# 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 by asking a question.

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

```
GET https://docs.zapsign.com.br/zapsign-api/english/create-check.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 `automate deployments from our CI pipeline` 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.