Integrations

SIP, carrier APIs,
Direct messaging and FHIR.

Independent inbound and outbound providers, account-specific rate rules, fax-engine telemetry and document interfaces. Connect these to the authorization and receipt model for each delivery.

Faxbot can work alongside an existing fax service or phone system. Bring the numbers and connections you use, then choose where to add routing, cost visibility and document handling.

Core connections

Fax providers

Choose sending and receiving providers independently. Built-in adapters include Phaxio, Sinch, the Telnyx Fax API, Documo, HumbleFax, eFax and SignalWire. Available sending, receiving and charge records depend on the provider and account.

SIP trunks and phone systems

Connect the Asterisk fax engine to your carrier trunk or office SIP phone system. Trace T.38 and G.711 fax paths, network boundaries and call outcomes. Existing Avaya IP Office and Aura installations have dedicated setup guidance.

Staff inboxes and document intake

Deliver received documents to the email inboxes staff already use. Applications can import a PDF and its source details into a mailbox, where ownership, acknowledgement and delivery evidence stay with the document.

Applications and AI assistants

Use the REST API, Python and Node.js SDKs, command line or MCP servers to connect your tools. Requests use a Faxbot identity and its permissions, so an integration gets the access you grant it.

Explore setup and API documentation →

In the current release

More ways to connect the work.

These capabilities are part of the current Faxbot release. We match deployment scope to the version, provider and receiving system you use.

Multiple accounts, trunks and sites

Manage several accounts at the same provider, independent sending and receiving paths, and trunks at different sites. Apply routing rules, capacity limits and account-specific prices to each delivery.

Email and folder workflows

Import documents from an email mailbox or a watched folder. Send by email or by dropping a document beside its destination instructions. Source identity and processing records keep a repeated read from creating another submission.

Direct messaging

Send and receive through configured Direct messaging accounts, with trust settings and delivery notices. The record distinguishes acceptance by a health information service provider from delivery to the recipient’s system.

FHIR document delivery

Deliver a PDF as a FHIR R4 DocumentReference to a confirmed endpoint using SMART Backend Services. A conditional create and document lookup handle repeated or uncertain requests.

Verified partner workflows

Verified direct delivery also carries fax images. After a broken transfer it resends only the missing pages or pieces, and it sends a partner only the bytes it doesn't already hold. Partners agree what they accept, and each transfer keeps its own outcome and evidence.

Measured document pricing

Cost-per-delivery routing measures the prepared document and the plan capacity still available. Compare the permitted routes before dialing, then reconcile estimates against reported carrier charges.

Custom integration

Finish the hand-off into your system.

Connect the transport to the work that follows: matching a document, filing it in the right record, assigning an owner and confirming receipt. We scope those steps around the interfaces your organization has enabled and the authority each action requires.

Clinical chart filing, case-system connectors, workforce provisioning and OCR or AI processing are integration work. The scope identifies the receiving system, the accepted document format and the evidence that shows the hand-off completed.

Start with the connection that needs work.

Tell us which carrier, phone system or application you use, where the document should arrive, and what happens when that hand-off fails.

Discuss your integration →