When should you use webhooks or polling?
Webhooks fit a workflow that needs a quick update and has a public HTTPS receiver you can operate. Polling can be simpler for a few occasional jobs or an application without an inbound endpoint. Read only unresolved jobs, wait between requests, and slow down when you hit the provider’s rate limit.
Which IDs should the receiver keep?
Store the provider’s notification ID separately from the fax ID and your own order or case ID. Verify the request using the provider’s documented method, then save the event or processing task before acknowledging it. Use a database constraint so receiving the same notification twice doesn’t record the business action twice.
What if a fax notification never arrives?
Read the original fax or Outbox record. If a provider replays a notification, apply it to the same fax record. When the original send outcome is unknown, leave it open for reconciliation. Restarting the fax itself could deliver a second copy.
How should you test before switching providers?
Use sample documents and a line you control. Confirm that one successful fax, one failure, a duplicate notification, and a withheld notification each leave the correct result in your application. If you will store webhook bodies, check whether their fields include phone numbers or email addresses and apply your retention policy.
Sources
Sources checked