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. Clear 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 encounter fax-only intake. The IRS accepts fax for some workflows, and courts may publish fax procedures. The need depends on the receiving institution.

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.
• Honest status reporting. The API must preserve unknown outcomes instead of inventing success or failure.
• Pay-per-use pricing. Not a monthly subscription for an API you call twice a week.
• Healthcare documentation. If you're building for healthcare, review vendor agreements and data handling for the entire workflow. Start with the healthcare fax requirements.
• Simple auth. API key in a header. Not OAuth flows for a fax.

Compare Current Fax APIs by Contract, Not Marketing Claims

Provider pricing, endpoints, status options, and compliance terms can change. Verify each candidate against its current first-party documentation before choosing it. This page does not treat old comparison numbers as current facts.

• Confirm whether outbound sending requires a rented number.
• Compare multipart upload, hosted-file, and callback models.
• Read every documented status, including unknown outcomes.
• Review rate limits, idempotency, and ambiguous-result guidance.
• Check current pricing against your actual page and send volume.
• For PHI, review every vendor agreement and eligible service.

FaxDrop focuses on outbound sending without a rented inbound number. Every signed-in account can create an API key. Browser and API sends use the same purchased and monthly included account credits and account limits.

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 form = new FormData();
form.append('recipientNumber', '+12125559876');
form.append('senderName', 'Your App');
form.append('senderEmail', 'operator@example.com');
form.append('file', file);

const response = await fetch('https://www.faxdrop.com/api/send-fax', {
  method: 'POST',
  headers: {
    'X-API-Key': 'fd_test_your_sandbox_key_here',
  },
  body: form,
});

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

Key differences from Twilio:

• Single API key instead of Account SID + Auth Token pair. Pass it in the X-API-Key header.
• No from number required. FaxDrop handles outbound number assignment. You provide only the recipient.
• Status polling is built in. UseGET /api/v1/fax/{faxId}to check queued, sending, completed, failed, partial, or unknown status.
• Paid credits deducted per fax (up to 10 uploaded pages per credit), not per page. Budget accordingly.

For full endpoint reference, authentication details, and status polling examples, see the FaxDrop developer docs.

Start with an fd_test_ sandbox API key. Before a live send, confirm the document and destination. If a result is queued or unknown, keep polling with backoff. Do not blindly retry because the first request may already have been accepted.

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

• Start with the job: outbound only, inbound numbers, or both.
• Test the failure path: confirm how unknown outcomes and retries work.
• Model the bill: use current first-party pricing and your real volume.
• Review regulated workflows: verify eligible services and agreements.
• Run a sandbox test: validate requests before any live send.