How are faxes secured?
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.
What file formats are supported?
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.
How long does a typical request take?
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.
Does the system automatically retry busy signals?
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.
Can I query the status of an outbound fax?
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.
Does the eFaxDeveloper automatically retry busy signals?
Yes. And, we can tailor our retry process to meet your specifications if needed.
I need to send thousands of pages a day; does eFaxDeveloper have enough capacity for my requirements?
Yes. Developer was designed specifically for high-demand fax applications.
How are faxes secured?
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.
What file format will I receive?
You can choose the file format that works best for you, either PDF or TIF.
What information is included in the wrapper data?
- The wrapper data includes:
- Date/time of fax receipt
- File type (PDF or TIF)
- Number of Pages
- CSID (Caller ID)
- 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)
How does barcode scanning work?
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.
Could I get a toll-free or international number for inbound faxing?
Yes. eFaxDeveloper has numbers in over 40 countries.
What bar coding symbologies are supported for inbound faxing?
eFaxDeveloper supports Datamatrix (highly recommended) and Code 39.
What development work will I need to do?
You will need to integrate your application so that it submits/captures faxes from the eFaxDeveloper API.
What delivery protocols are available?
HTTPS POST is the only protocol currently offered.
What developmental support is available?
Each SDK comes with detailed documentation including code samples. Technicians are available to assist, if needed.
How are the transmissions secured?
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.
I already have a fax number that I'm using; can I port it over for use with eFaxDeveloper?
Yes. We can easily port most numbers.
Do I need a fax server in order to run the eFaxDeveloper API?
No fax server is required. eFaxDeveloper is an outsourced solution requiring no dedicated faxing hardware.