> For the complete documentation index, see [llms.txt](https://docs.commercelayer.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.commercelayer.io/core-api-reference/notifications.md).

# Notifications

The notification object and the allowed CRUD operations on the related resource endpoint

Notification can be attached to some resources and fetched (also by sales channels) by [including](/core/including-associations.md) them as an association when retrieving the resource they belong to (which is referenced in the `notifiable` attribute).

Notifications can be created manually via API (you need to use [integration](/core/api-credentials.md#integration) API credentials). In some cases, they are automatically generated by some specific integrations with external services. The notification message and/or any other related information is stored within the `body` JSON object.

Notifications can be marked as `flash`. Flash notifications are temporary and will be deleted each time a new notification of the same type is created.

{% hint style="warning" %}
The `flash` feature is enabled only for notifications automatically generated based on the specific integration setup. Setting the attribute to `true` for notifications manually created via API currently has no effect.
{% endhint %}

{% hint style="info" %}
At the moment, notifications are available for [orders](/core-api-reference/orders.md), [line items](/core-api-reference/line_items.md), and [shipping methods](/core-api-reference/shipping_methods.md) (in the future, the feature will be extended to other resources).
{% 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.commercelayer.io/core-api-reference/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.