Replay a notification
Changed onAttempts 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.
Request
- Base URLhttps://sandbox-api.paddle.com
- AuthHTTP bearer
Path parameters
Paddle ID of the notification entity to work with.
Response
The request has been accepted for processing, but processing has not yet completed.
Example response
{
"data": {
"notification_id": "ntf_01ghbkd0frb9k95cnhwd1bxpvk"
},
"meta": {
"request_id": "b15ec92e-8688-40d4-a04d-f44cbec93355"
}
}Changes
- breaking
added the new path request parameter
notification_id - breaking
the
response's property type changed fromobjectto no type for status - breaking
removed the required property
/from the response with the status - breaking
removed the required property
/from the response with the status - breaking
removed the required property
/from the response with the status - breaking
removed the required property
/from the response with the status - warning
removed the optional property
/from the response with the status - info
added to the
response propertyallOflist for the response status - info
the response property
became required for the status - info
the response property
/became required for the status - info
the response property
became required for the status - info
the response property
became required for the status - info
the response property
became required for the status
- breaking
- info
api tag
Notificationsadded - info
api tag
Notification setting replaysremoved
- info