> You are reading the Docusign Developer Documentation. For clean Markdown of any page, append .md to the page URL.
>
> Documentation indexes by section:
> - APIs and SDKs: https://docusign.docs.buildwithfern.com/docs/llms.txt
> - Platform 101: https://docusign.docs.buildwithfern.com/platform/llms.txt
> - Extension Apps: https://docusign.docs.buildwithfern.com/extension-apps/llms.txt
> - Docusign CLI: https://docusign.docs.buildwithfern.com/docusign-cli/llms.txt
>
> Authentication (OAuth, JWT Grant, M2M): https://docusign.docs.buildwithfern.com/platform/auth
> Webhooks and Connect: https://docusign.docs.buildwithfern.com/platform/webhooks
>
> OpenAPI specifications: https://docusign.docs.buildwithfern.com/openapi.json
> MCP server: https://docusign.docs.buildwithfern.com/_mcp/server

# How to set up HMAC security with your app

> See how to set up Docusign Connect HMAC security with your app.

This topic describes how to [add](/platform/webhooks/connect/setting-up-hmac#add-hmac-keys-for-your-app) and  [remove](/platform/webhooks/connect/setting-up-hmac#remove) HMAC keys for your app.

## Add HMAC keys for your app

You can opt in to [Using HMAC Security with Docusign Connect](/platform/webhooks/connect/hmac) for your Docusign Connect account using the following steps:

1. Log in to your Docusign account in either the developer or production environment.
2. From the top menu, select **Admin**.
3. Select **Connect** in the **INTEGRATIONS** section in the left menu.
4. In the horizontal navigation at the top of the Connect page, select **Connect Keys**, then generate at least one HMAC key by choosing **Add Secret Key**.

   > **Important:** The full content of each secret key is only visible directly after creation. Make sure that you record it when it’s created and store its value securely. For security reasons, only the first four characters of the key display in the eSignature Settings UI on subsequent views.
5. In the horizontal navigation at the top of the Connect page, select **Configurations**; then open an existing custom Connect configuration or create a new one.
6. Scroll down to the **Integration and Security Settings** section and select the **Include HMAC Signature** checkbox.
7. Select **Add Configuration** or **Save Configuration** to save the change.

> **Note:** Docusign recommends using one key when possible. If you need to rotate keys, see [Remove HMAC keys](/platform/webhooks/connect/setting-up-hmac#remove-hmac-keys) for best practices.

You can also configure Connect to use HMAC via the REST API. The methods to [create](/docs/esign-rest-api/reference/connect/connectconfigurations/create) or [update](/docs/esign-rest-api/reference/connect/connectconfigurations/update) your Connect configurations now support an additional HMAC boolean parameter that, if set to `true`, enables HMAC security for that account. If you plan to use the API to enable HMAC, you must still [define at least one HMAC key](/platform/webhooks/connect/setting-up-hmac#add) first in the eSignature Settings as described above. HMAC keys cannot be added via the API.

![An image of the integration and security settings page that has the 'include HMAC signature (recommended)' setting selected. It is followed by a list of secret keys.](/_fern-files/_img/7d58ebd0cbcc4d216ec77601479c580cf08e350d1d3e0548f280c762418c1e5e.webp)

## Remove HMAC keys

You can remove a secret key at any time by opening the **Connect Keys** page on your app's Connect configuration page in eSignature Admin, then selecting **Remove** next to the key. This will remove the key from your configuration and shift each key below it up; for example, if you had defined four keys and then deleted key 2, key 3 would become the new key 2 and key 4 would become the new key 3.

> **Note:** Because deleting a key will shift the values of each key below it, this can require changes to how the signature headers are computed.

To rotate keys, Docusign recommends that you stop your app, delete the key to be rotated, create a new key, add it to your app, then restart your app.

![An image of the 'Connect' settings page, with the 'Connect Keys' tab selected. It includes a list of secret keys, with the option to add or remove keys.](/_fern-files/docusign.docs.buildwithfern.com/3ab02ea6a92c2e0a26fe4dfe7f81d2d713fcf82069bb9c7299e99fa6d5f652ca/assets/img/ctf/vqQtZ31QLh7vbCOchue3r-HmacKeys.png)

## Next steps

* See [How to validate a webhook message using HMAC](/platform/webhooks/connect/validate).
* See [Using HMAC Security with Docusign Connect](/platform/webhooks/connect/hmac) for context about HMAC.