Integrate the eFax API.Caddi writes and runs the integration for you.
eFax has a REST API (the eFax Enterprise API) with webhooks. eFax opens the Enterprise API to eFax Corporate accounts and trusted partners rather than to anyone with a developer login. Each integration gets an API key and App ID, which it exchanges for a bearer token.
- 99%of agent runs complete successfully
- ~45 minon average to build your first agent
- 1M+back-office tasks completed
The connection is a project before it does anything.
Before the first record moves: an app registration, credentials, token refresh, and somewhere to host and monitor the code.
Register an app, store eFax credentials, refresh tokens.
Connect your eFax account once. Caddi holds the connection.
The job doesn't stop at eFax.
An intake, a filing or a client update also runs through email, documents and the other systems your team works in. The eFax API only reaches eFax.
Each extra system is another API, another set of credentials, another integration to own.
One automation runs across every tool the job touches, each through its API.
Someone has to own the code.
API versions change, fields get added and your process moves.
A developer patches and redeploys the integration each time.
The person who does the work updates it by showing or describing the change. Every automation is reviewed before it runs in production, and every run is logged.
What the eFax API gives you
- Type
- REST (JSON)
- Authentication
- OAuth 2.0 (API key and App ID exchanged for a bearer token)
- Who can get access
- eFax opens the Enterprise API to eFax Corporate accounts and trusted partners rather than to anyone with a developer login. Each integration gets an API key and App ID, which it exchanges for a bearer token.
- What it covers
- Sending faxes, downloading fax images and metadata, searching sent and received faxes, deleting faxes, and webhooks for inbound and outbound fax notifications; a separate Admin API handles account provisioning and numbers.
Official docs: docs.efaxcorporate.com. Checked October 2026. Vendors change access terms, so confirm with eFax before you build.
When to build the eFax integration in-house
When you have engineers and the integration is your product, or you need one narrow sync between two systems and someone to own it. When the goal is getting eFax work off someone's desk, the build is the slow part, and Caddi does it for you.
What teams usually want the eFax API for
File inbound faxes
Caddi reads each inbound eFax, identifies the client or matter, and files it in the right system.
Extract and update records
Caddi pulls the fields from a faxed form and updates the client record in the CRM.
Send from workflow
Caddi sends the outbound eFax and confirms delivery back in Outlook.
Everything Caddi does with eFax.
eFax API questions
Does eFax have an API?
Yes. eFax has a REST API (the eFax Enterprise API) with webhooks, authenticated with OAuth 2.0 (API key and App ID exchanged for a bearer token). The official documentation is at https://docs.efaxcorporate.com/API/content/index.htm.
How do I get access to the eFax API?
eFax opens the Enterprise API to eFax Corporate accounts and trusted partners rather than to anyone with a developer login. Each integration gets an API key and App ID, which it exchanges for a bearer token.
Can I connect eFax to my other tools without writing code against its API?
Yes. With Caddi you show the eFax task once, the way you'd train a new hire, and Caddi builds it as verified code that runs across eFax and the other tools the job touches. Steps that need a person's judgment are handed to Copilot or Claude, and Caddi monitors those too.
Do I need a developer to automate eFax with Caddi?
No. There is no integration code for you to write or maintain. Every automation Caddi builds for eFax is reviewed before it runs in production, and every run is logged.