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

# License Feature Events

Events emitted when license-level product features are created, updated, or deleted.

License features are product features assigned to a specific license. Each feature has its own limits and usage.

Use the [event data objects](https://docs.licensespring.com/events-api/event-list/event-data-objects.md) reference for field definitions. For consumption events, see [consumption pool and offline checkout events](https://docs.licensespring.com/events-api/event-list/consumption-pool-and-offline-checkout-events.md).

{% hint style="warning" %}
**Changes made on the Vendor Platform license page do not emit license feature events.**

Those changes also do not emit `license.updated`. To capture every feature change, retrieve the license features through the Management API.
{% endhint %}

### Event reference

#### `license_product_feature.created`

Sent when the Management API adds a feature to a license.

**Not emitted when**

* The feature is added from the Vendor Platform license page.
* A license edit or license policy adds the feature.
* A product feature is added to every license for a product.
* A scheduled update adds the feature.

**Event data:** `license_product_feature`

#### `license_product_feature.updated`

Sent when one of the following occurs:

* The Management API changes a license feature.
* **Add Feature Consumption** records consumption for the feature. This also emits `license_product_feature.consumption_added`.
* A device deactivates and reports feature consumption.

**Not emitted when**

* The feature's consumption resets through its consumption period.
* A pool reset or license reset resets consumption.
* A scheduled update changes the feature.
* The Vendor Platform license page changes the feature.

**Event data:** The license feature. Its location in `data` depends on the trigger.

#### `license_product_feature.deleted`

Sent when the Management API removes a feature from a license.

**Not emitted when**

* The Vendor Platform license page removes the feature.
* A product feature is removed from every license at once.
* The product feature is deleted.
* A scheduled update removes the feature.

**Event data:** The license feature before deletion. It is available at `data.product_feature`.

### Event data location

All three events include the same license-feature fields. The fields appear at different paths depending on the event and trigger.

| Event                             | Trigger                                        | Feature data path                         |
| --------------------------------- | ---------------------------------------------- | ----------------------------------------- |
| `license_product_feature.created` | Management API                                 | `data.license_product_feature`            |
| `license_product_feature.updated` | Management API                                 | `data.product_feature`                    |
| `license_product_feature.updated` | Add Feature Consumption or device deactivation | `data` directly, without a wrapper object |
| `license_product_feature.deleted` | Management API                                 | `data.product_feature`                    |

{% hint style="info" %}
Check each possible path in your event handler. Here, `data.product_feature` is a **license** feature. It is not the product feature object described in [Product events](https://docs.licensespring.com/events-api/events-list/product-events).
{% endhint %}


---

# 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/license-feature-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.
