> For the complete documentation index, see [llms.txt](https://developers.make.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.make.com/event-subscription/implementation/verify-signatures.md).

# Verify signatures

{% hint style="warning" %}
Signature verification is optional but recommended. Use it to confirm that a request came from Make and verify the integrity of the signed request data.
{% endhint %}

The delivery ID, timestamp, and signature follow the [Standard Webhooks 1.0 specification](https://github.com/standard-webhooks/standard-webhooks/blob/b2fa7b8719fb75d326b591077f5d1b385cfcdfae/spec/standard-webhooks.md). Make defines the event envelope and schemas separately in [Event types](https://developers.make.com/event-subscription/reference/event-types.md) and adds `Webhook-Topic` as routing metadata.

Each subscription has a signing secret beginning with `whsec_`. You can obtain the current secret from the subscription details in Make. Store it in a secret manager and expose it only to the receiver that performs verification.

{% hint style="warning" %}
Never put the signing secret in source control, logs, error messages, analytics, or the destination URL.
{% endhint %}

### Verify a request <a href="#verify-a-request" id="verify-a-request"></a>

Verification uses the exact raw request body, `Webhook-Id`, `Webhook-Timestamp`, `Webhook-Signature`, and the subscription's signing secret. Verify the raw body before JSON parsing or any transformation; parsing and serializing it again can change the signed bytes.

You can implement the following steps directly or use a compatible [Standard Webhooks reference library](https://www.standardwebhooks.com/) for your language.

The signed content has this format:

```
<Webhook-Id>.<Webhook-Timestamp>.<raw request body>
```

1. Require all three signature headers and retain their values as received.
2. Interpret `Webhook-Timestamp` as Unix time in seconds. As a replay-protection recommendation, reject the request if it differs from the current time by more than 5 minutes in either direction.
3. Remove the `whsec_` prefix from the signing secret and Base64-decode the remainder to obtain the HMAC key.
4. Construct the signed content shown above using the header values and exact raw body.
5. Compute HMAC-SHA256 over the signed content and Base64-encode the binary digest using standard Base64.
6. Split `Webhook-Signature` on spaces. For each entry beginning with `v1,`, compare the supplied digest with the computed digest using a constant-time comparison.
7. Accept the signature if any supported `v1` entry matches. Otherwise, reject the request without processing it.

Do not compare signatures with a normal string equality operation. Keep the receiver's clock synchronized and verify immediately on receipt.

Timestamp freshness limits replay of a captured signed request. It does not replace [`Webhook-Id` deduplication](https://developers.make.com/event-subscription/implementation/retries-duplicates-and-ordering.md#deduplicate-with-webhook-id), which prevents a legitimate retry or manual resend from triggering the same action or update more than once.

A valid signature confirms authenticity and integrity; it does not validate the JSON or event schema. After verification, parse and validate the event. For a valid but unknown `{type, version}`, see [Handle unknown events](https://developers.make.com/event-subscription/implementation/handle-unknown-events.md).


---

# 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://developers.make.com/event-subscription/implementation/verify-signatures.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.
