FaxDrop API

Developer Changelog

API changes that can affect developers, MCP clients, automation, rate limits, status polling, and integration behavior.

2026-05-28

API-key delivered email suppression

POST /api/send-fax, terminal notifications, MCP clients, and batch senders

What changed: API-key sends can pass sendEmail=false to suppress delivered-fax confirmation emails for a specific fax. FaxDrop stores the per-fax preference on the fax status record and echoes deliveryEmail as enabled or suppressed in the success response.
Behavior impact: The default remains sendEmail=true. Consumer web sends keep delivered emails enabled. Failed-fax emails, status pages, refunds, and operator alerts still run. Status polling and reconcile treat the suppressed delivered email as satisfied so healthy completed faxes do not stay pending.
Action needed: Batch API clients that rely on status polling for audit records may pass sendEmail=false. Clients that want email confirmations should omit the field or pass sendEmail=true.

2026-05-26

Developer API, MCP clients, status polling, and rate limits

What changed: FaxDrop aligned terminal success on completed, split API-key send and status polling limits, exempted valid API-key sends from the anonymous IP cap, and added a per-fax status refresh throttle.
Behavior impact: API-key sends use the send_fax policy at 10/min, 30/hr, and 500/day. Status polling uses the status_poll policy at 60/min, 500/hr, and 2000/day. Active status polls refresh from Sinch at most once every 10 seconds per fax ID.
Action needed: Treat completed as terminal success. Treat older delivered wording as a legacy alias. Use the X-RateLimit-Policy and status freshness headers when tuning client polling.

Security & Compliance

HIPAA Compliant

Signed BAA on file · No document retention

PCI DSS Level 1

Payments secured by Stripe · No card data touches our servers

256-bit SSL

End-to-end TLS 1.2+ encryption in transit

Zero Retention

Files deleted immediately after transmission completes