> 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/get-started/event-subscriptions.md).

# Event subscriptions

Event subscriptions deliver events from Make to a public HTTPS endpoint you control. Each delivery is an HTTP `POST` request with a JSON body.&#x20;

{% hint style="info" %}
**Design for duplicate and out-of-order deliveries.** Event subscriptions use at-least-once delivery. The same delivery can be sent more than once, and events are not guaranteed to arrive in the order they occurred.

For more information, see, [Retries, duplicates, and ordering](https://developers.make.com/event-subscription/implementation/retries-duplicates-and-ordering.md).
{% endhint %}

### Build your integration

Your integration needs to handle the following:<br>

* [Receive events](https://developers.make.com/event-subscription/implementation/receive-events.md): request format, delivery headers, event envelope, and acknowledgment behavior
* [Event types](https://developers.make.com/event-subscription/reference/event-types.md): available events, payload schemas, field definitions, and examples
* [Retries, duplicates, and ordering](https://developers.make.com/event-subscription/implementation/retries-duplicates-and-ordering.md): retry and resend behavior, duplicate handling, and delivery ordering
* [Verify signatures](https://developers.make.com/event-subscription/implementation/verify-signatures.md): optional but recommended verification that a request came from Make
* [Handle unknown events](https://developers.make.com/event-subscription/implementation/handle-unknown-events.md): behavior for event types or versions your integration doesn't recognize

### Choose which events to receive

Make offers two subscription levels:

* All events - Selecting **All events** includes every event type available to the subscription, including types added later.
* Slected events - Selecting **Selected events** includes only the selected event types and doesn't expand automatically.

If you use **All events**, account for event types added later. Your integration should also define how it handles an unknown event version. For more information about handling unrecognized events, see [Handle unknown events](https://developers.make.com/event-subscription/implementation/handle-unknown-events.md).

For instructions on creating and managing subscriptions, see the [Event subscriptions](https://help.make.com/event-subscriptions) article in the Make Help Center.

### Test and diagnose

Use [Test and diagnose deliveries](https://developers.make.com/event-subscription/operations/test-and-diagnose-deliveries.md) to test the delivery path, validate example payloads, and investigate failed deliveries.

### Permissions to manage event subscription

Access to manage Event Subscriptions is restricted by a specific custom role permission.<br>

* **Default Access**: Organization Owners and Admins automatically get this permission.
* **Custom Roles**: Any other user role must explicitly be granted the Event subscriptions permission to view or manage event subscriptions.

For more information, see [Permissions for event subscriptions](https://help.make.com/event-subscriptions#permissions-for-event-subscriptions) documentation.&#x20;


---

# 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/get-started/event-subscriptions.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.
