Event types
fax.failed
Sent when a fax has failed terminally.
WEBHOOK
When it fires
Exactly once, when no further delivery attempt will be made. Two paths reach here:- Retries exhausted. Every retryable attempt up to
max_attemptsfailed. - Terminal error code returned. A code classified as terminal (for example,
invalid_number,bad_destination,no_route) was returned by an attempt. Remaining retries are skipped.
What your handler should do
- Branch on
error_codeto choose the next step. The codes are mintfax-owned and stable across carrier changes - they will not churn under you. error_messageis human-readable English, suitable for showing in your dashboard. The agent-actionable contract iserror_code.- The full
attempts[]array is included. Each entry carries its ownerror_code- useful when you want to see whether the failure was, say, threebusyretries vs an immediateinvalid_number. fax.failedandfax.deliveredare mutually exclusive. The fax will not silently succeed after this event.
Acting on common codes
See Errors for the full code list including codes that return as 422 at submission time rather than as
fax.failed.Authorizations
API key as Bearer token. Use an account key (mfx_acct_...) for
/account/* endpoints, and an environment key (mfx_test_... for
sandbox, mfx_live_... for live) for /environment/*, /faxes,
/webhooks, and /events.
Body
application/json
Event delivery to your subscribed webhook endpoint.
Webhook delivery for fax.failed.
Event identifier (evt_-prefixed). Stable across retry attempts.
Example:
"evt_8aZqRm4yT3vK7pNxJ2bH9c"
Event type. Always fax.failed for this delivery.
Available options:
fax.failed Unix epoch seconds when the event was generated.
Response
2XX
Acknowledged. mintfax treats any 2xx response as a successful delivery.
Last modified on July 20, 2026