> 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/webhooks/como-funciona.md).

# How webhooks works

Set up your webhooks in less than 1 minute.

Webhooks **are automatic notifications essential for system integration,** as they notify your server directly, eliminating the need to constantly check the status of an operation. \
\
**With webhooks, you can:**

* <mark style="background-color:blue;">**Reduce repetitive API**</mark> <mark style="background-color:blue;"></mark><mark style="background-color:blue;">queries to check the status of a document (commonly known as polling);</mark><br>
* <mark style="background-color:blue;">**Synchronize systems and integrations**</mark><mark style="background-color:blue;">, ensuring that information between different platforms is always up to date and consistent;</mark><br>
* <mark style="background-color:blue;">**Automate post-event**</mark> <mark style="background-color:blue;"></mark><mark style="background-color:blue;">processes so that subsequent tasks are performed automatically.</mark>

{% hint style="info" %} <mark style="color:red;">**Do I need to have an API Plan to use webhooks?**</mark>**&#x20;No, webhooks are freely available** to all users. But API users are strongly recommended to use webhooks instead of polling.
{% endhint %}

***

**ZapSign supports webhooks to notify you of events such as document creation, signature, document rejection, document completion, or email delivery failure.** When such an event occurs, we send an HTTP POST request to the URL configured in your application containing details about the event in JSON format.

{% hint style="warning" %}
Your application s**hould return status 200 when receiving a webhook**, otherwise, ZapSign will retry the sending, generating duplicates and/or unnecessary requests.
{% 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/webhooks/como-funciona.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.