Work with notification destinations
Create notification destinations to tell Paddle which events you'd like to receive and where to deliver them to. Once added, you can update, deactivate and reactivate, and delete destinations.
A notification destination is a webhook endpoint or email address that Paddle sends notifications about events to. It's sometimes called a notification setting.
How it works
When something notable occurs in your system, Paddle creates an event entity with information about what happened and when.
Notification destinations let you get notifications when events happen. You can get notifications by email or as webhooks.
Webhooks are typically used to keep your app in sync with Paddle. For example, when a subscription cancels, Paddle can send a subscription.canceled
notification as a webhook. When you receive this event, you can provision access to your app to make sure the canceled customer can no longer access your app.
Notifications include the event entity in the payload, so you can see the new or changed entity.
Create a notification destination
Create a notification destination to start receiving notifications for events. You can choose the kind of events that you'd like to receive notifications for.
You can create as many notification destinations as you like, but only 10 may be active at once.
Create new destination
Go to Paddle > Developer Tools > Notifications.
Click New destination.

Enter details
Enter the details for your new notification destination.
Description | Short description for this notification destination. |
Notification type | Whether you'd like to send events to a webhook endpoint or an email address. |
URL or email | Webhook endpoint URL or email address to send events to. |
API version | API version that returned objects for events should conform to. |

Choose events and save
Choose the events that you'd like to receive notifications for.
Click Save destination when you're done.

Update a notification destination
Once you've created a notification destination, you can change its name, destination URL or email, whether sensitive fields are included, and the events received.
To change other fields, deactivate this notification destination and create another.
Edit destination
Go to Paddle > Developer Tools > Notifications.
Click the … next to a notification destination in the list, then choose Edit destination from the menu.

Change details and save
Edit notification destination details and events.
Click Update destination when you're done.

Deactivate a notification destination
Deactivate a notification destination to stop Paddle from sending notifications for events to it. Deactivation is useful if you need to make changes to a webhook endpoint server or integration. You can reactivate later, if needed.
Go to Paddle > Developer Tools > Notifications.
Click the … next to a notification destination in the list, then choose Deactivate from the menu.
You can reactivate later by choosing Activate from the menu.

Delete a notification destination
Delete a notification destination to permanently remove it from your Paddle system. Paddle stops sending notifications for events to your destination, and you'll lose access to all the logs for this notification destination.
There's no way to recover a deleted notification destination. Deactivate a notification destination if you'll need access to the logs or want to reactivate later on.
You can only delete notification destinations using the API.
Request
Send a DELETE
request to the /notification-settings/{notification_setting_id}
endpoint.
Paddle ID of the notification entity to work with.
API
List notification destinations by making a GET request to the /notification-settings
endpoint. Work your way through the results to find the notification destination that you'd like to work with.
Dashboard
Head to Paddle > Developer Tools > Notifications, click the … icon next to a notification destination in the list, then choose Copy ID.
Response
If successful, Paddle returns 204 No Content
with no response body.