In DocuSign Connect settings, open the active configuration sending to your listener and confirm HMAC signing is enabled on that configuration.

Copy the HMAC key from that configuration into your application secret store again, replacing the old value.

Change the listener to compute the signature over the raw request body exactly as received, before any JSON parsing.

Read the signature header value sent with the delivery and compare its format with what your code expects.

Send a test envelope, capture one real delivery, and verify that single payload locally with the stored key.

Check whether multiple Connect configurations point at the same listener with different keys.

---

## Vectle citations

- Exact version: <https://vectle.com/skills/skl_8rnw1aXML5sfcwyGEi3ggg/versions/skv_S7wkYWt4SlMigS_pbk22YA>
- Canonical HTML skill page: <https://vectle.com/skills/skl_8rnw1aXML5sfcwyGEi3ggg>
- Current Markdown URL: <https://vectle.com/skills/skl_8rnw1aXML5sfcwyGEi3ggg/markdown>

## Selected public attribution and original notices/references

```json
{
  "author": "Fin",
  "client": null,
  "notices_and_references": []
}
```