> For the complete documentation index, see [llms.txt](https://docs.emsigner.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.emsigner.com/administrator-settings/admin-settings/webhook.md).

# Webhook

What is webhook and how do I configure it in emSigner?

In emSigner, a webhook is a mechanism that allows the system to send real-time notifications to other applications or systems when certain events occur. When a predefined action or event takes place in emSigner-like document signing or workflow completion-the webhook sends an HTTP POST request to a specified URL (the webhook endpoint) in the external system.

This request contains data about the event, enabling the external system to process it further, such as updating a database, triggering other workflows, or notifying users.

For example, if you want an external system to be notified immediately after a document is signed, you could configure a webhook in emSigner to send a notification to that system's endpoint. This integration approach is beneficial for automating workflows and keeping multiple systems synchronized in real-time.

**Step 1: Log in to your emSigner account**\
Click on the **Settings** tab in the top navigation bar. Under **Integrations & Automation**, click on the **Webhooks for Real-Time Updates** card.

<figure><img src="https://1693119202-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXNKpOPGIHdEkmaF2RQso%2Fuploads%2FaJQJZTROqb6R6lyRwVdb%2Fimage.png?alt=media&amp;token=4d99bc53-e710-4838-9222-beb7b568231f" alt=""><figcaption></figcaption></figure>

**Step 2: Create a new webhook**\
On the Webhooks for Real-Time Updates page, click **Create New** in the top-right corner.

<figure><img src="https://1693119202-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXNKpOPGIHdEkmaF2RQso%2Fuploads%2FeD8iGLKexj3TC6G2VJ4r%2Fimage.png?alt=media&amp;token=509d9715-8b29-41ce-9732-48dc69a8fcb1" alt=""><figcaption></figcaption></figure>

**Step 3: Enter the webhook details**\
On the Create Webhook page, enter the relevant details in the respective fields:

* **Name** — a friendly label for your webhook, used only for display
* **Department** — select the department from the dropdown; the webhook will apply only to activities linked to that department
* **Request From** — enter the source of the request
* **Event** — tick the necessary checkbox(es) for the event(s) you want to track: Recalled, Declined, Completed, Signed/Reviewed, Custom Status, or Voided
* **Target** — enter the target URL to which data will be sent. HTTPS is recommended. You can click **Send** to test the endpoint before saving
* **Authentication** — select the authentication scheme for your target URL, or choose "None" if it doesn't require one

<figure><img src="https://1693119202-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXNKpOPGIHdEkmaF2RQso%2Fuploads%2FtVblY7A3Ngx9rYedige8%2Fimage.png?alt=media&amp;token=a93ff4d2-3b26-4939-9c79-32718aeef3f1" alt=""><figcaption></figcaption></figure>

**Step 4: Save the webhook**\
Once all the information is provided, click **Save**.

**Step 5: Verify the webhook**\
The newly created webhook will appear in the Webhooks for Real-Time Updates list with its Name, Request From, Event, Authentication, and Status (Active) displayed. Use the pencil icon in the **Actions** column to edit the webhook, or the trash icon to delete it.

<figure><img src="https://1693119202-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXNKpOPGIHdEkmaF2RQso%2Fuploads%2FuJi1vNly2WLEs7NWItR2%2Fimage.png?alt=media&amp;token=c3d2786b-dce2-46c3-83a5-0bfc3dfc51dd" alt=""><figcaption></figcaption></figure>

* Users can track the status of documents based on the information related to different action events sent to the endpoint.
* Events like Recalled, Declined, Completed, Signed/Reviewed, Custom Status, and Voided can be ticked as per requirement.
* Upon successful completion of any one of the above-mentioned events, a notification will be triggered and JSON data will be pushed to the webhook endpoint with the document status details.