Overview
Webhook logs and replay help you monitor outbound webhook activity, troubleshoot failures fast, and keep downstream systems in sync. From a single screen you can filter events, inspect payloads, review delivery history, and retry failed attempts—no engineering lift required.
Who can use this
- Roles: Account Owners and Admins
- Requirements: Your account must be configured to send webhooks
What you can do here
- Filter webhook deliveries by multiple criteria
- Resend failed webhooks (single or in bulk)
- View the exact request payload and headers
- Review the full delivery history (attempts, timestamps, response codes)
Filter your webhook logs
Use the filters at the top of the page to quickly zero in on the events you care about.
Available filters include:
- Status: Delivered, Failed, Retrying, Queued
- Event Type: (e.g., order.created, return.approved, etc.)
- Endpoint URL: Target listener URL
- Date & Time Range: Custom start/end
- HTTP Response Code: 2xx, 4xx, 5xx
Steps
- Navigate to Settings → Integrations → Webhooks and API.
- Scroll down to the Webhook Logs section.
- Select the desired filters and click Apply.
- If needed, click Reset Filters to do another search.
Best practices & tips
- Start with filters: Narrow to a specific event type + time window to accelerate triage.
- Check the response body: Many endpoints return helpful error messages (auth, schema, rate limits).
- Validate signatures: If you use signing, confirm your verification logic when troubleshooting 401/403 errors.
- Fix downstream first, then replay: Replaying before fixing the root cause will likely fail again.
- Monitor patterns: Repeated 5xx suggests endpoint instability; 4xx often indicates auth or contract issues.
FAQs
Does replay change the payload?
No. Replays send the original payload to the same endpoint.
Can I change the endpoint on replay?
No. Replays target the original endpoint for traceability and integrity.
How many times can I replay?
There’s no hard cap, but we recommend fixing the underlying issue before repeated retries.
Do you store payloads?
Payloads are stored for log visibility and replay. Retention follows account policy and compliance standards.
Summary
The Webhook Logs & Replay feature centralizes webhook observability and remediation. Navigate to Settings → Integrations → Webhooks and API → Webhook Logs to filter deliveries, inspect payloads and responses, review attempt history, and safely replay failures—so your integrations stay resilient and your teams move faster.
Comments
0 comments
Article is closed for comments.