
Selecting an Endpoint
The Events tab is scoped to one endpoint at a time. Use the dropdown at the top to switch between your registered webhook destinations. The performance metrics and delivery log below update to reflect only that endpoint’s activity.Performance Overview
The top panel summarizes delivery health for the selected endpoint over the chosen time range.
The chart plots successful and failed attempts over time. A rising failed line means your endpoint is returning errors or becoming unreachable. Use it alongside your server logs to triage delivery degradation quickly.
Time range: Use the dropdown at the top right of the chart to change the reporting window. The default is the last 7 days.
Endpoint Details
The right panel on the Events tab shows the configuration for the selected endpoint at a glance:- Name: The label you gave this destination.
- URL: The HTTPS address deliveries are sent to. Click the copy icon to grab it without revealing the full path in your browser history.
- Events: The event types this endpoint is subscribed to. The count badge shows how many subscriptions are active.
- Created At: When the endpoint was registered.
- Signing secret: The HMAC secret used to sign deliveries to this endpoint. Masked by default. Click the eye icon to reveal it or the copy icon to grab it directly.
Delivery Attempts
Below the performance chart, every delivery attempt to the selected endpoint is listed in reverse chronological order.
Click Refresh to pull the latest attempts without reloading the page.
Inspecting an Event
Click any row in the delivery attempts table to open the event detail panel.
Payload: The complete JSON body that was
POSTed to your endpoint. This is exactly what your server received. Click the copy icon to grab the full payload for use in local testing or debugging.
Retrying an Event
Click Retry on any event detail to re-deliver that event to the endpoint. Bachs enqueues a new delivery attempt immediately. The original event payload is sent again, not regenerated. Use this to recover from transient failures, server downtime, or misconfigured handlers without waiting for a new event to fire.Retry delivers the original payload. If your handler is idempotent (which it should be), retrying is always safe. Check the
id field in the envelope to deduplicate if needed.Replay Events
Re-deliver any past event to your endpoint via the API.
Webhooks
Manage your endpoint destinations and signing secrets.
Logs
Trace the API requests that triggered these events.

