---
description: Does emSigner support multiple webhook configurations for different systems?
---

# Multiple Webhooks

Yes, in emSigner, you can configure multiple webhooks. This allows you to send real-time updates to different source systems based on specific events.

**Use Case:** Multi-System Webhook Integration in emSigner

**Scenario:** XYZ Bank uses emSigner for digital document signing across multiple departments—Loans, HR, and Compliance. Each department requires real-time updates in their respective systems whenever a document is signed. To achieve this, emSigner allows configuring multiple webhooks with a "Request From" parameter to ensure updates are routed to the correct system.

**How It Works:**

* The Loan Department configures a webhook (https://lms.xyzbank.com/api/loan-updates) with "Request From": "LoanManagement", ensuring loan agreements are automatically updated in the Loan Management System (LMS) once signed.
* The HR Team sets up a webhook (https://hrportal.xyzbank.com/api/employee-onboarding) with "Request From": "HRPortal", allowing the HR system to mark new employees as "Onboarded" after signing Offer Letters and NDAs.
* The Compliance Team integrates a webhook (https://compliance.xyzbank.com/api/audit-logs) with "Request From": "ComplianceAudit", ensuring all signed contracts are logged in the Audit & Compliance System for regulatory tracking.

With Multi-System Webhooks, emSigner enables businesses to streamline their document workflows, ensuring every department gets real-time updates without manual intervention.



**Event-Based Configuration** – You can configure webhooks for different types of events, such as document status updates, signing completion, or user actions.

**Multiple Destinations** – Organizations can define different webhook URLs for different departments or systems, ensuring that relevant updates are routed to the right destination.

**Webhook Retry Mechanism** – If a webhook fails, emSigner has a retry mechanism that will attempt to send the update again based on configurable intervals.

**Webhook Failure Alerts** – If a webhook continuously fails, an alert is sent to the Super Admin, informing them that the webhook needs to be fixed.

Below are the steps to configure multiple webhooks.

**Step 1:** Navigate to the Settings Page of the Administrator account.

**Step 2:** Locate the ‘Webhook’ tile under the Admin Settings.

**Step 3:** The gird with the existing webhooks configured will be shown in the ‘List of Configured Webhooks’.

<figure><img src="https://1693119202-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXNKpOPGIHdEkmaF2RQso%2Fuploads%2FJmVqpNG7JXh4DOnxIXce%2Fimage.png?alt=media&#x26;token=438c2214-8311-490a-8adc-55fb0f0339ca" alt=""><figcaption></figcaption></figure>

**Step 4:** The admin has to provide the Name, the events for which this webhook needs to be configured.

**Step 5:** For the default webhook URL, the admin can skip selecting the department or the Request From.

<figure><img src="https://1693119202-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXNKpOPGIHdEkmaF2RQso%2Fuploads%2FuDGLMVkJ8Zk577cdKPWn%2Fimage.png?alt=media&#x26;token=7bb15a2d-6255-4430-a57d-73bf463009b7" alt=""><figcaption></figcaption></figure>

**Step 6:** If there are multiple source systems then the admin has to mandatorily provide either the Department Name or the Request From parameter. This Request From parameter has to be mandatorily passed in the API so that the emSigner system identifies that for any change in the workflow status of this envelope the particular Source System has to be notified.

<figure><img src="https://1693119202-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXNKpOPGIHdEkmaF2RQso%2Fuploads%2FGQBHOxNmU4niORTBFiXb%2Fimage.png?alt=media&#x26;token=e340fe9b-5f50-4fef-9d68-8bad270b9126" alt=""><figcaption></figcaption></figure>

**Step 7:** The admin has to select the type of authentication, if there is no authentication then None needs to be selected or else Basic needs to be selected. Once all the details are filled in, the admin has to save the webhook configuration.

<figure><img src="https://1693119202-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXNKpOPGIHdEkmaF2RQso%2Fuploads%2F39LBy5XT5n9FrQkFs1ZO%2Fimage.png?alt=media&#x26;token=bb399b9c-87a3-48f5-bb86-6ce18dab2f3f" alt=""><figcaption></figcaption></figure>
