bunnyfaxbunnyfax.com

Fax API checklist for sending, receiving and retries

A fax API trial should prove that you can send the exact prepared PDF, reconcile an uncertain submission without duplicating it, find the inbound document, and trace both directions to the invoice. Use a harmless sample and a fax line you control.

Sources checked

1. Review the exact document before sending

Prepare a two-page PDF with a distinct marker on each page. Record the prepared document ID, page count and destination. Verify that the review record refers to that exact version and that changing the file or recipient requires another review when your workflow needs approval.

2. Reconcile a lost response before trying again

Use a test environment to simulate a lost response after the service accepts the request. Record the client request ID and confirm whether the provider returns the original attempt on retry or offers a status lookup. A timeout can leave a real fax in progress.

3. Reconcile duplicate or delayed status events

Deliver a sample status event twice to your test integration. Both copies should resolve to one fax record. If an older pending event arrives after a terminal event, check that your integration keeps the correct final outcome. Record whether polling is available if a webhook never arrives.

4. Verify who can open the inbound document

Send a sample into your receiving number and record when the PDF becomes available. With a restricted test credential, verify that the workflow can open only the intended inbox. Revoke the credential and check that a later download request is denied.

5. Reconcile usage in both directions

Record the outbound and inbound counts, include any cover page, and compare the result with billing. If the provider meters time, preserve transmission minutes and the charges as well as pages. Check how failed attempts and reserves affect the available allowance.

Sources