From request to outcome
- Submit the fax once from Send fax or your authorized integration.
- Follow the exact record in Sent. Queued/preparing reflects accepted work and document preparation; a capacity delay does not prove transmission.
- Read the current delivery evidence, not only processing completion or an older notification.
- Check independent document and notification outcomes if those are part of your workflow.
Delivered means positive delivery confirmation. Could not deliver needs review of the latest failure and retry state. Confirmation delayed, unavailable, incomplete or conflicting means delivery remains uncertain; it does not establish that the fax was sent or that nothing happened. Wait for fresh evidence or ask support before resending.
API reply lost
Use the current developer reference for the same-request Idempotency-Key contract. A correlation ID alone is not idempotency. Repeating with a new key or creating a new fax may duplicate a transmission. Reconcile the original request first.
Webhook notifications
Open Developers → Webhooks and inspect your configured endpoint privately. Compare the event/time and your receiver's response. Check reachability, enabled configuration and the documented signature/authentication verification in your receiver. Never share the endpoint secret or raw event payload with support. Missing/out-of-order callbacks require reconciliation. A callback failure does not mean fax failure; fax resend is not callback repair. Unsupported replay/test controls remain unavailable. The current customer API reference is at https://docs.faximus.io/.
Safe support details
For help, open Help in your signed-in Faximus account and copy support details. Provide only the page, request or fax reference if shown, approximate time/timezone and expected versus observed behavior. Do not share fax contents, medical details, passwords, verification codes, API keys, payment details, document links or raw logs. Support may need independent identity/account verification.