> For the complete documentation index, see [llms.txt](https://docs.licensespring.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.licensespring.com/events-api/event-list/events-and-email-notifications.md).

# Events and Email Notifications

How consumption webhooks and email notification policies work together.

Consumption webhooks and email notifications work independently. Use either mechanism, or use both.

| Delivery method         | Audience                                      | Configuration                                |
| ----------------------- | --------------------------------------------- | -------------------------------------------- |
| **Email notifications** | Customers, license managers, or license users | Notification policies in the Vendor Platform |
| **Webhook events**      | Your systems                                  | **Settings → Webhooks**                      |

### Email and webhook mapping

| Email notification                                                              | Sent when                                            | Matching webhook event                            |
| ------------------------------------------------------------------------------- | ---------------------------------------------------- | ------------------------------------------------- |
| Max consumptions reached (`max_consumptions_reached`)                           | A license reaches its effective limit                | `license.consumption_max_reached`                 |
| Max consumptions perc reached (`max_consumptions_perc_reached`)                 | License usage rises above a percentage in the policy | None                                              |
| Max feature consumptions reached (`max_feature_consumptions_reached`)           | A product feature reaches its effective limit        | `license_product_feature.consumption_max_reached` |
| Max feature consumptions perc reached (`max_feature_consumptions_perc_reached`) | Feature usage rises above a percentage in the policy | None                                              |
| Max pool consumptions reached (`max_pool_consumptions_reached`)                 | A pool reaches its effective limit                   | `consumption_pool.consumption_max_reached`        |

When you use both mechanisms, a limit-reaching call sends one email and one webhook.

{% hint style="info" %}
Percentage thresholds have no matching webhook. To respond before a limit is reached, compare `total_consumptions` and `max_consumptions` in `consumption_pool` or `license.updated` events. Alternatively, keep a percentage-based email notification policy.
{% endhint %}

### Important behavior

#### Percentage notifications

* Percentage emails are emitted only when usage increases. Negative consumption never emits one.
* Percentage and limit emails do not stack. The call that reaches the limit sends only the **reached** email.
* Pools have no percentage email. They have only the **reached** email.

#### Limits and delivery

* A pooled license or feature retains its own limit. It can emit its own **reached** email and event when its `max_consumptions` limit is reached, even when the pool has remaining units.
* An email failure never fails the API call. The system sends emails after saving consumption.


---

# 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://docs.licensespring.com/events-api/event-list/events-and-email-notifications.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.
