Skip to main content
POST
/
notifications
/
{notification_id}
/
replay
Replay a notification
const options = {method: 'POST', headers: {Authorization: 'Bearer <token>'}};

fetch('https://api.paddle.com/notifications/{notification_id}/replay', options)
  .then(res => res.json())
  .then(res => console.log(res))
  .catch(err => console.error(err));
{
  "data": {
    "notification_id": "ntf_01h46h1s2zabpkdks7yt4vkgkc"
  },
  "meta": {
    "request_id": "cfe92cac-86a1-49fe-ac50-20620dcd024f"
  }
}

Authorizations

​
Authorization
string
header
required

Requests are authenticated with API keys. Provide your API key as a Bearer token in the Authorization header.

API keys are assigned permissions, granting them access to entities and operations. Each endpoint may require one or more permissions, defined with the x-permissions extension. Values for include parameters may require specific permissions as defined in the x-enum-permissions extension. See all available permissions in the permission schema or documentation.

Get an API key and select the permissions you need from the Paddle dashboard under Paddle > Developer Tools > Authentication.

Path Parameters

​
notification_id
string
required

Paddle ID of the notification entity to replay. Must be a notification with the origin of event.

Example:

"ntf_01gt261ms8ew72a0vnm5p5ne2q"

Response

Accepted

​
data
object
​
meta
Meta · object

Information about this response.