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

# Replay notifications

Resend a notification that's failed or delivered using the new replay a notification operation.

---

## What's new?

We added the [replay a notification operation](https://developer.paddle.com/api-reference/notifications/replay-notification.md) to the Paddle API. You can use it to resend a [notification](https://developer.paddle.com/api-reference/notifications/overview.md) using its ID.

{% api-endpoint method="POST" path="/notifications/{notification_id}/replay"  %}

- **notification_id** (string): Unique Paddle ID for this notification, prefixed with `ntf_`
{% /api-endpoint %}

## How it works

The new [replay a notification operation](https://developer.paddle.com/api-reference/notifications/replay-notification.md) lets you replay a notification, attempting to send it again.

You can replay notifications that have the status of `delivered` or `failed`. Other kinds of notification are still being delivered or retried by Paddle, so you can't replay them.

When you replay a notification, Paddle creates a new notification entity for it and returns the new `notification_id` in the response. The new notification entity is related to the same `event_id` as the original notification entity.

## 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 [replay a notification](https://developer.paddle.com/api-reference/notifications/replay-notification.md) using the API to get started.
## Summary of changes

| Name | Type | Change | Entity | Description |
| --- | --- | --- | --- | --- |
| POST Replay a notification | API operation | added | Notifications |  |