All posts are performed using Secure Socket Layers (SSL) with 128-bit encryption, plus user authentication and optional IP restriction. This service facilitates compliance with GLB, HIPAA and other important security and privacy regulations.
eFax Developer supports the following file formats: Microsoft Word, Microsoft Excel, Adobe PDF, Plain Text, HTML and TIF Image files. Support for additional file formats is available.
We will dial the fax number within about 30-90 seconds (depending on the document submitted). The fax itself will take about 30-45 seconds per page to transmit. You will receive status information within about 15 seconds after the fax completes. For a typical, one-page fax, the entire process takes less than 2 minutes.
Yes, we use a dynamic retry process to maximize the likelihood of delivery while minimizing the impact of incorrect numbers. For example, a standard busy signal will result in up to 5 retries, spaced over increasing delays between each retry. But a "human answered" error will result in just one retry attempt. We can tailor our retry process to meet your specifications.
Yes. Your fax status will automatically be posted back to you immediately following the end of the fax transmission, but you can also requery at any time.
Yes. And, we can tailor our retry process to meet your specifications if needed.
Yes. Developer was designed specifically for high-demand fax applications.
Posts from eFax Developer can be made using Secure Socket Layers (SSL) with 128-bit encryption. You control the URL we post to and can certainly supply an HTTPS URL.
You can choose the file format that works best for you, either PDF or TIF.
- The wrapper data includes:
- Date/time of fax receipt
- File type (PDF or TIF)
- Number of Pages
- CSID (Caller ID)
- ANI
- Fax Status
- MCFID (eFax's id for the fax)
- Number of barcodes scanned (if applicable)
- Barcode value (if applicable)
- Barcode sequence (if applicable)
- Barcode scan direction (if applicable)
- Barcode symbology (if applicable)
- Barcode page number (if applicable)
- Barcode coordinates on page (if applicable)
When an inbound fax is received, our system will scan and read the barcode image (Data matrix or Code 39) on the document and feed the barcode value and the fax itself back to you within the XML Post.
Yes. eFaxDeveloper has numbers in over 40 countries.
eFaxDeveloper supports Datamatrix (highly recommended) and Code 39.
You will need to integrate your application so that it submits/captures faxes from the eFaxDeveloper API.
HTTPS POST is the only protocol currently offered.
Each SDK comes with detailed documentation including code samples. Technicians are available to assist, if needed.
All posts are performed using Secure Socket Layers (SSL) with 128-bit encryption. This service facilitates compliance with GLB, HIPAA and other important security and privacy regulations.
Yes. We can easily port most numbers.
No fax server is required. eFaxDeveloper is an outsourced solution requiring no dedicated faxing hardware.
Questions?
(866) 761-8111
Privacy