Updates a notification setting (notification destination) using its ID.
When updating subscribed events, send the complete list of event types that you’d like to subscribe to — including existing event types. If you omit event types, they’re removed from the notification setting.
You only need to pass an event type name. Paddle responds with the full event type object for each event type.
If successful, your response includes a copy of the updated notification setting entity.
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.
Paddle ID of the notification setting entity (notification destination) to work with.
"ntfset_01gt21c5pdx9q1e4mh1xrsjjn6"
Represents a notification destination when updating notification destinations.
Short description for this notification destination. Shown in the Paddle Dashboard.
1 - 500Webhook endpoint URL or email address.
1 - 2048Whether Paddle should try to deliver events to this notification destination.
API version that returned objects for events should conform to. Must be a valid version of the Paddle API. Can't be a version older than your account default. Defaults to your account default if omitted.
x >= 1Whether potentially sensitive fields should be sent to this notification destination.
Subscribed events for this notification destination. When creating or updating a notification destination, pass an array of event type names only. Paddle returns the complete event type object.
Type of event sent by Paddle, in the format entity.event_type.
address.created, address.imported, address.updated, adjustment.created, adjustment.updated, api_key.created, api_key.expired, api_key.expiring, api_key.revoked, api_key.updated, business.created, business.imported, business.updated, customer.created, customer.imported, customer.updated, discount.created, discount.imported, discount.updated, payment_method.saved, payment_method.deleted, payout.created, payout.paid, price.created, price.imported, price.updated, product.created, product.imported, product.updated, report.created, report.updated, subscription.activated, subscription.canceled, subscription.created, subscription.imported, subscription.past_due, subscription.paused, subscription.resumed, subscription.trialing, subscription.updated, transaction.billed, transaction.canceled, transaction.completed, transaction.created, transaction.paid, transaction.past_due, transaction.payment_failed, transaction.ready, transaction.revised, transaction.updated Whether Paddle should deliver real platform events, simulation events or both to this notification destination.
platform, simulation, all