Every delivery attempt mintfax makes is recorded. When a webhook does not arrive, this is where you look first. The same data is available in the dashboard and through the API.
What is recorded per attempt
In the dashboard
Settings > Webhooks lists every registered endpoint. Click an endpoint to see its delivery history, filterable by status and event type. Each attempt expands to show the headers and response. A failed attempt has a “Retry now” action that re-sends the same event payload to the same endpoint immediately.
Via the API
List attempts for an environment:
Retrieve a single attempt with full request and response detail:
Trigger an immediate retry:
A manual retry counts as attempt N+1 for that event. The original scheduled retry sequence continues independently if the automatic schedule has not yet been exhausted.
See the Webhooks API reference for the full parameter set.
Common failures and what they mean
When you fix something on your side
After a deploy that fixes a webhook bug, you have two options to recover lost events:
- Wait for the next scheduled retry. If you are still inside the automatic retry window (about 18 minutes from the first attempt), mintfax will deliver the event again on its own.
- Retry manually. From the dashboard or via
POST /webhooks/attempts/{id}/retry. This is what you want for events that exhausted their automatic retries.
If you missed a batch of events while your endpoint was down, the Events API is the source of truth - you can iterate through events from any point in time and re-process them, even if no webhook delivery would still retry.
Next
Last modified on July 14, 2026
