> 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/receive-events.md).

# Receive events

Make delivers each event to the HTTPS endpoint configured as the subscription's destination. In this guide, **endpoint** means the HTTP route that receives a delivery, and **receiver** means the service behind that endpoint.

### Request contract <a href="#request-contract" id="request-contract"></a>

Make sends each event as an HTTP `POST` request with a JSON body to the subscription's public HTTPS destination URL.

Do not configure a URL that redirects. Make expects the configured destination itself to receive and acknowledge the request.

### Example request <a href="#example-request" id="example-request"></a>

The following example shows the request line, delivery headers, and event body together. The signature value is illustrative.

```
POST /make-events HTTP/1.1
Host: events.example.com
Content-Type: application/json
Webhook-Id: ed31c148-7017-5eac-bef7-9e9600057ce1
Webhook-Timestamp: 1781006401
Webhook-Signature: v1,BASE64_SIGNATURE
Webhook-Topic: scenario.created

{
  "type": "scenario.created",
  "timestamp": "2026-06-09T12:00:00.000Z",
  "version": 1,
  "data": {
    "scenario_id": 999,
    "user_id": 42,
    "team_id": 7,
    "organization_id": 100
  }
}
```

### Request headers

HTTP header names are case-insensitive.

<table data-header-hidden="false" data-header-sticky><thead><tr><th>Header</th><th>Description</th></tr></thead><tbody><tr><td>Content-Type</td><td>application/json</td></tr><tr><td>Webhook-Id</td><td>Stable delivery identifier. It remains the same across automatic retries and manual resend. Use it as the deduplication key.</td></tr><tr><td>Webhook-Timestamp</td><td>Unix time in seconds when the delivery attempt was sent. It can change between attempts.</td></tr><tr><td>Webhook-Signature</td><td>One or more space-separated v1,&#x3C;signature> values used to verify the request.</td></tr><tr><td>Webhook-Topic</td><td>Event type, such as scenario.created. Use the body type field as the canonical routing value.</td></tr></tbody></table>

{% hint style="info" %}
Don't use Webhook-Timestamp or Webhook-Signature to identify duplicates because both values can change between attempts.
{% endhint %}

Make doesn't send an attempt-number header. Detect repeat attempts by the repeated Webhook-Id, and use Make's delivery information when you need the attempt history.

### Event envelope

Every body has the same top-level structure:

```
{
  "type": "scenario.created",
  "timestamp": "2026-06-09T12:00:00.000Z",
  "version": 1,
  "data": {
    "scenario_id": 999,
    "user_id": 42,
    "team_id": 7,
    "organization_id": 100
  }
}
```

The following table describes each field:

<table data-header-hidden="false" data-header-sticky><thead><tr><th>Field</th><th>Type</th><th>Description</th></tr></thead><tbody><tr><td><code>type</code></td><td>string</td><td>Customer-facing event type. Route events using this field together with version.</td></tr><tr><td><code>timestamp</code></td><td>string</td><td>UTC date and time when the event occurred, formatted as ISO 8601. This isn't the attempt time in the Webhook-Timestamp header.</td></tr><tr><td><code>version</code></td><td>integer</td><td>Schema version for this event type. It isn't a global API version.</td></tr><tr><td><code>data</code></td><td>object</td><td>Event-specific fields. For more information, see <a href="https://developers.make.com/event-subscription/reference/event-types.md">Event types</a>.</td></tr></tbody></table>

The body doesn't include an event ID. Use the Webhook-Id header as the stable delivery identifier.

### Acknowledge deliveries

Return a direct `2xx` response when your endpoint is ready for Make to stop automatically retrying the delivery.

You can acknowledge with `200 OK`, `202 Accepted`, or `204 No Content`. Make doesn't require a particular response body. Make may retain the response body with the delivery attempt. Keep the body small, and don't include secrets or sensitive data.

If your application already accepted the same `Webhook-Id`, return `2xx` without acting on the event again.

If your endpoint doesn't accept the event, return an appropriate non-`2xx` response. Make treats the attempt as failed and may retry it.

The following table summarizes Make's behavior for each response:

<table data-header-hidden="false" data-header-sticky><thead><tr><th>Result from your endpoint</th><th>Make behavior</th></tr></thead><tbody><tr><td>Direct <code>2xx</code></td><td>Make considers the request acknowledged.</td></tr><tr><td><code>3xx</code></td><td>Unsupported. Don't redirect event subscription requests.</td></tr><tr><td><code>4xx</code> or <code>5xx</code></td><td>The attempt fails and is eligible for automatic retry.</td></tr><tr><td>Timeout, DNS, connection, or TLS failure</td><td>The attempt fails and is eligible for automatic retry.</td></tr></tbody></table>

For more information about the retry schedule and recovery behavior, see [Retries, duplicates, and ordering](https://developers.make.com/event-subscription/implementation/retries-duplicates-and-ordering.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/receive-events.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.
