Search notification logs
Search notification logs with filtering and pagination.
- Start date and end date cannot be more than 30 days apart
- Either
orgIdorpaypointIdmust be provided
This endpoint requires the notifications_create OR notifications_read permission.
Authentication
Bearer authentication of the form Bearer <token>, where token is your auth token.
Long-lived API token sent in the requestToken header. See API token authentication.
Query parameters
Request
The start date for the search. Can’t be more than 30 days before endDate.
The end date for the search. Can’t be more than 30 days after startDate.
The event to filter by, such as approvedpayment. Case-insensitive.
Filter by delivery outcome. Set to false to return only failed notifications.
The ID of the organization to filter by. Either orgId or paypointId is required.
The ID of the paypoint to filter by. Either orgId or paypointId is required.
Response
The notification’s delivery method — 1 (Email), 2 (SMS), or 3 (Webhook).
The name of the paypoint the notification is related to. Empty for organization-level notifications.
The ID of the paypoint the notification is related to. Null for organization-level notifications.
The event that triggered the notification, such as approvedpayment.
The HTTP status code the target returned, such as 200. Returns 0 when the target sent no response.
The delivery status message, such as OK when the notification succeeded, Dropped when it failed, or No response received from server. when the target sent no response.