> For the complete documentation index, see [llms.txt](https://developer.paddle.com/llms.txt).

# Get all notifications for a customer, subscription, or transaction

Find all notifications that relate to a customer, subscription, or transaction entity, and filter notifications by date period.

---

## What's new?

We added new query parameters that you can use when working with [the list notifications operation](https://developer.paddle.com/api-reference/notifications/list-notifications.md) to filter returned entities.

{% api-endpoint method="GET" path="/notifications"  %}

- **from** (string): Return entities from a specific time. Pass an RFC 3339 datetime string
- **to** (string): Return entities up to a specific time. Pass an RFC 3339 datetime string
- **filter** (string): Return entities that contain the Paddle ID specified. Pass a transaction, customer, or subscription ID
{% /api-endpoint %}

## How it works

The new `from` and `to` query parameters let you filter notifications by date. For example, you can use them to return notifications that happened in the last day, week, or another period.

The new `filter` query parameter lets you filter notifications that relate to transactions, subscriptions, or customers using their relevant Paddle IDs. For example, you can find all notifications that relate to a particular customer. This isn't just limited to notifications for customer events, it includes notifications for any events that relate to that customer — including subscriptions or transactions for them.

## Examples

{% accordion %}
{% accordion-item title="Notifications for a date period" %}

This example returns notifications that occurred during May 2023.

{% api-endpoint method="GET" path="/notifications?from=2023-05-01T00:00:00Z&to=2023-06-01T00:00:00Z"  %}

{% /api-endpoint %}

{% /accordion-item %}
{% accordion-item title="Notifications for a customer" %}

This examples returns notifications for a customer. It includes all notifications that relate to the customer, including subscriptions and transactions for them.

{% api-endpoint method="GET" path="/notifications?filter=ctm_01h2asct98zxebssbkt1q6tfyr"  %}

- **filter** (string): Return entities up to a specific time. Pass an RFC 3339 datetime string
{% /api-endpoint %}

{% /accordion-item %}
{% /accordion %}

## Next steps

This change is available in version `1` of the Paddle API.

It's a non-breaking change, meaning it doesn't impact existing integrations.

You can [list notifications](https://developer.paddle.com/api-reference/notifications/list-notifications.md) using the API to start using the new query parameters.
## Summary of changes

| Name | Type | Change | Entity | Description |
| --- | --- | --- | --- | --- |
| `from` | Field | added | List notifications | Filter notifications by start date. |
| `to` | Field | added | List notifications | Filter notifications by end date. |
| `filter` | Field | added | List notifications | Filter by customer, subscription, or transaction ID. |