Twilio Fax Is Dead. Here's What to Use Instead in 2026.

Why Twilio Killed Fax

Twilio's Programmable Fax was one of the cleanest fax APIs ever built. Simple REST endpoints. Webhooks for delivery status. Pay-per-page pricing. Developers loved it because it worked exactly like you'd expect a modern API to work.

But Twilio decided fax was not core to their communications platform. They announced the deprecation in mid-2021 and fully shut it down by December of that year. No migration path. No partner recommendation. Just a sunset notice.

The problem: fax did not go away just because Twilio stopped supporting it. Healthcare, legal, government, and financial services still run on fax. Over 70% of healthcare providers use fax for medical record transfers. The IRS accepts fax. Courts accept fax. The demand did not shrink. The supply did.

What Developers Actually Need from a Fax API

If you were using Twilio Fax, you probably valued these things:

• REST API with JSON responses. Not SOAP. Not XML. Not a form submission that returns HTML.
• Webhook callbacks for delivery status. You do not want to poll. You want to be notified when the fax lands or fails.
• Pay-per-use pricing. Not a monthly subscription for an API you call twice a week.
• HIPAA compliance. If you're building for healthcare, the fax provider needs a BAA and zero-retention policy.
• Simple auth. API key in a header. Not OAuth flows for a fax.

Fax API Comparison: FaxDrop vs Fax.Plus vs Telnyx vs Notifyre

These are the actively maintained fax APIs in 2026. Here's how they compare on the factors developers care about:

FaxDrop charges per fax (up to 10 pages per credit), not per page. For low-volume developers and AI agents sending occasional faxes, that pricing model beats per-page billing. No DID rental required. No monthly minimum.

Telnyx is a strong choice if you need phone numbers and fax in the same platform. They have the most developer-friendly infrastructure, but you pay for a dedicated fax number (DID) even if you only send outbound.

Fax.Plus has a polished API and solid documentation, but their pricing is subscription-based. That works fine for steady volume. Not great for bursty or infrequent use cases.

Notifyre is AU-based and works well for Australia/NZ fax. Not HIPAA compliant, so skip it for US healthcare use cases.

Code Migration: From Twilio to FaxDrop API

The core pattern is the same. You POST a request with a recipient number and a document. Here's a side-by-side showing what the call looked like in Twilio vs what it looks like in the FaxDrop API.

// Twilio Fax (deprecated Dec 2021)
const client = require('twilio')(accountSid, authToken);

const fax = await client.fax.v1.faxes.create({
  from: '+12025551234',
  to: '+12125559876',
  mediaUrl: 'https://example.com/document.pdf',
});

console.log(fax.sid); // FXxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

// FaxDrop REST API
const response = await fetch('https://www.faxdrop.com/api/fax', {
  method: 'POST',
  headers: {
    'Authorization': 'Bearer YOUR_API_KEY',
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
    to: '+12125559876',
    documentUrl: 'https://example.com/document.pdf',
    webhookUrl: 'https://your-app.com/fax-webhook', // optional
  }),
});

const { faxId, status } = await response.json();
console.log(faxId); // fax_xxxxxxxxxxxxxxxx

Key differences from Twilio:

• Single API key instead of Account SID + Auth Token pair. Pass it as a Bearer token.
• No from number required. FaxDrop handles outbound number assignment. You provide only the recipient.
• webhookUrl is optional. If provided, FaxDrop POSTs delivery status (delivered, failed, busy) to your URL.
• Credits deducted per fax (up to 10 pages per credit), not per page. Budget accordingly.

For full endpoint reference, authentication details, and webhook payload schema, see the FaxDrop developer docs.

The AI Agent Angle: Why Fax APIs Matter More Now

Here's what's changed since Twilio killed fax: AI agents are everywhere. And AI agents that interact with healthcare systems, government agencies, and legal institutions need to send faxes. Not because fax is good technology. Because fax is what those institutions accept.

An AI agent processing a prior authorization needs to fax it to the insurance company. An AI agent filing paperwork with a county clerk needs to fax the form. An agent helping someone send documents to the IRS needs a fax endpoint it can call.

This is why fax APIs are having a quiet comeback. The demand is not from humans who love fax. It's from software that needs to talk to systems that only speak fax.

How to Choose the Right Fax API in 2026

• Low or unpredictable volume (1-50 faxes/month): FaxDrop. Pay per fax, no minimum, no DID rental.
• HIPAA use case with high volume: Telnyx or Sinch. Both have BAAs and volume pricing.
• Subscription-based product with steady fax volume: Fax.Plus. Clean API, good documentation, predictable monthly cost.
• Australia or New Zealand: Notifyre. Built for APAC fax infrastructure.
• Need phone numbers AND fax in the same platform: Telnyx. Best multi-product developer platform.