Subotiz Webhooks notification logs allow merchants to view event delivery records, delivery results, and server responses, and to manually resend webhook notifications when needed. This helps merchants troubleshoot failed webhook events and resend notifications after issues are resolved.
Notification Logs Overview
Webhook notification logs record the full delivery lifecycle of events sent to a configured endpoint, including delivery status, request payloads, and server responses.
- Access path: Go to Developer > Webhooks, then click any existing webhook endpoint to access its notification logs.
- Log retention scope: Only webhook notification records from the most recent 30 days are displayed. Records older than 30 days are not shown on this page.
- Search and filtering rules: The notification log page supports filtering to help quickly locate specific event records.
- Search: Supports fuzzy search by event name (for example:
.unpaid).Note: Search currently supports event names only. Order IDs, subscription IDs, endpoint URLs, and request content are not supported.
- Status filter: Filter notification records by delivery status:
- Successful
- Failed
- Time range filter: Supports filtering by date range, limited to records within the most recent 30 days.
Webhook Details
- Available information
- Event name: The webhook event type that was triggered (for example,
v2.subscription.unpaid). - Delivery status: The delivery result of the event.
- Created time: The system-recorded time when the notification was created and sent, used for log sorting and filtering.
Notification logs are displayed in descending order by creation time, with the most recent events shown first.
- Webhook delivery status: The delivery status indicates the outcome of an individual webhook notification.
- Successful: The webhook was successfully delivered to the endpoint and a valid response was received.
- Failed: The webhook was not successfully delivered, or the destination server returned an error response.
- Notification details: Click any notification record to view full delivery details.
- Basic information
- Event name
- Endpoint URL
- Delivery status
- Delivery time
- Request duration
- Request content
- Displays the original request payload sent to the merchant’s server.
- Supports one-click copy for local debugging or troubleshooting.
- Response content
- Displays the original response returned by the merchant’s server.
- Can be used to confirm whether the request was processed successfully and to identify error causes.
Manually Resending Webhook Notifications
After confirming that an issue has been resolved, merchants can manually resend webhook notifications.
- Applicable scenarios
- Authentication or permission issues have been corrected.
- Server-side errors have been resolved.
- Firewall or network restrictions have been removed.
- Business logic needs to be re-triggered.
- How resending works
- Click Resend on the notification details page.
- The system sends the same request payload to the original endpoint.
- Each resend creates a new notification record.
- Original records are not modified or overwritten.
Note: Use the resend function only after confirming that the underlying issue has been resolved to avoid duplicate or invalid business requests.
Webhook Troubleshooting Recommendations
If a webhook notification is not received, follow these steps to troubleshoot:
- Check the notification logs to confirm whether the event record exists.
- Review the delivery status to determine whether it is marked as failed.
- Open the notification details and review the response error information.
- After resolving the issue, use the manual resend function to trigger the notification again.
By using webhook notification logs and manual resend functionality, merchants can gain clear visibility into event delivery and independently resolve webhook issues without manual intervention, improving integration stability and operational efficiency.