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

# Product Events

Events emitted when products, features, custom fields, and installation files change.

Product events report changes to products and product-level resources made through the Vendor Platform or Management API.

Use the [event data objects](https://docs.licensespring.com/events-api/event-list/event-data-objects.md) reference for field definitions.

### Products

#### `product.created`

**Sent when:** a product is created.

**Not emitted when:** Products are imported from a CSV file.

**Event data:** `product`

#### `product.updated`

**Sent when:**

* a product is edited,
* a product is enabled or disabled (`active` changes),
* a product is archived or restored (`is_archived` changes). Archiving also changes the product's `short_code`: it gets `.archived.` and a timestamp appended, and restoring puts the original back.

**Not emitted when:** Enabling, disabling, archiving, or restoring does not change the product because it already has that state. The event is also not emitted when products are added to or removed from a bundle, or imported from a CSV file.

**Event data:** `product`, after the change

{% hint style="info" %}
Products cannot be deleted. They can only be archived. To detect a product being taken out of use, handle `product.updated` where `is_archived` is `true`.
{% endhint %}

### Product features

#### `product_feature.created`, `product_feature.updated` and `product_feature.deleted`

**Sent when:** a feature is created, edited or deleted on a product.

**Not emitted when:** Features are imported from a CSV file.

**Event data:** `product_feature`. For `deleted`, it reflects the feature before deletion, so `is_deleted` remains `false`.

{% hint style="info" %}
Deleting a product feature also removes it from every license that has it. Those licenses do not emit `license_product_feature.deleted`.

Adding or removing a feature from every product license at once also does not emit license feature events.
{% endhint %}

### Product custom fields

#### `product_custom_field.created`, `product_custom_field.updated` and `product_custom_field.deleted`

**Sent when:** a custom field is created, edited or deleted on a product.

**Event data:** `product_custom_field`. For `deleted`, it reflects the custom field before deletion.

{% hint style="info" %}
Deleting a product custom field also removes its values from every license. Those licenses do not emit `license_custom_field.deleted`.
{% endhint %}

### Installation files

#### `installation_file.created`, `installation_file.updated` and `installation_file.deleted`

**Sent when:** an installation file is added to, edited on or deleted from a product.

**Event data:** `installation_file`. For `deleted`, it reflects the installation file before deletion.


---

# 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/product-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.
