Update Notification
Update a notification or autogenerated report.
Authorizations
Most endpoints require an organization token. Some endpoints require an application token, and those endpoints are noted.
Path Parameters
Notification ID.
Body
Information about the standard notification configuration (email, sms, web).
one-time, untilcancelled Get near-instant notifications via email, SMS, or webhooks for important events like new payment disputes, merchant activations, fraud alerts, approved transactions, settlement history, vendor payouts, and more. Use webhooks with notifications to get real-time updates and automate operations based on key those key events. See Notifications for more.
email, sms, web ID for the paypoint or organization that owns the notification.
Entity owner type. Accepted values:
0: Organization/partner2: Paypoint
0, 2 Specify the notification target.
- For method=email the expected value is a list of email addresses separated by semicolon.
- For method=sms the expected value is a list of phone numbers separated by semicolon.
- For method=web the expected value is a valid and complete URL. Webhooks support only standard HTTP ports: 80, 443, 8080, or 4443.
Status of notification:
0: Inactive1: Active
0, 1 Response
If isSuccess = true, responseData contains the notification identifier.
If isSuccess = false, responseData contains the reason for the error.
Auxiliary validation used internally by payment pages and components.
Code for the response. Learn more in API Response Codes.
When the request was successful, this contains the notification ID, or nID used to manage the notifcation.
Response text for operation: 'Success' or 'Declined'.
Was this page helpful?