# POST /notifications/{notification_id}/replay

**Replay a notification**

Attempts to resend a `delivered` or `failed` notification using its ID.

Paddle creates a new notification entity for the replay, related to the same `event_id`. Your response includes the new `notification_id` of the created notification.

Notifications older than 90 days aren't retained. If you try to replay a notification that's no longer retained, Paddle returns an error.

Only notifications with the `origin` of `event` can be replayed. You can't replay a notification created for a replay.

**Required permissions:** `notification.write`

## Path parameters

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `notification_id` | string | required | Paddle ID of the notification entity to work with. |

## Response (202)

- `data`: object (required) — Represents a notification replay entity.
  - `notification_id`: string (required) — Unique Paddle ID for this notification, prefixed with `ntf_`. (pattern: `^ntf_[a-z\d]{26}$`)
- `meta`: object (required) — Information about this response.
  - `request_id`: string (required) — Unique ID for the request relating to this response. Provide this when contacting Paddle support about a specific request.

### Response example

```json
{
  "data": {
    "notification_id": "ntf_01h46h1s2zabpkdks7yt4vkgkc"
  },
  "meta": {
    "request_id": "cfe92cac-86a1-49fe-ac50-20620dcd024f"
  }
}
```