Live data from Hacker News

Programmable Fax – API for sending and receiving faxes

twilio.com

71–80 of 174 posts

Re: Programmable Fax – API for sending and receiving faxes

#73

Earlier quoted context omitted.

Phaxio founder here. Our pricing might seem higher (and may be in certain situations), but it works a bit differently that Twilio's. Twilio charges you the 1c _plus_ the costs of the call. Phaxio is an "all in" rate _including_ retrying the call. And, at Phaxio, if the calls all fail there's no cost to you. I'm not saying that we won't adjust our pricing (#competition), but there's a difference in the actual unit cos…

How long does it take to send a page of fax? Their pricing is 0.007 per minute. I haven't seen many fax machines take more than a minute per page, but they would have to take 10 minutes to catch up to your pricing. Edit: Fixed time to comparable pricing.

Quick answer is that it depends on what's on the page. It can be as quick as a minute or significantly longer if there are images or lots of data the page.

Re: Programmable Fax – API for sending and receiving faxes

#74

This is neat! But I have to expose the PDF to the internet for Twilio to pick up the file and send it? https://www.twilio.com/docs/api/fax/quickstart#send-a-fax

Certainly you can attach a token and firewall all but twilio's servers if you're serious about using this service.

I don't see the problem with it.

Re: Programmable Fax – API for sending and receiving faxes

#75
post #48
post #12

Earlier quoted context omitted.

A lot of the Uber-for-food-delivery startups use them for ordering at restaurants because there is no text-based API to restaurants and the UX of receiving an automated phone call is poor. They're pervasive in finance, insurance, employee benefits, etc. They're also a good one-to-many API multiplexer. So many businesses can take a fax and have a human operate on it that many software companies can use them to add act…

For years the operating procedure for Seamless/Grubhub/Delivery.com orders was a form that would be faxed to a restaurant, the restaurant would communicate that order to the kitchen (either by it's own POS system, writing the order on a regular order ticket or even giving the kitchen the fax sheet) and then the service would call the restaurant and the employee would enter the confirmation code into the phone. Some r…

Kitchens are still a rough place for technology, and even though the latest iPhone might survive a drop in the toilet, I don't want to drink the soup after a phone's taken a swim in it.

I've seen tablets in cafes at the front of the house, and sometimes the cashier (who can't touch food while they're also touching money) copies the order off the tablet and onto a piece of paper and passes it off to the kitchen the old fashioned way, while acknowledging it was received on the tablet.

Re: Programmable Fax – API for sending and receiving faxes

#76
If anyone's first reaction was along the lines of: "Faxing in 2017?" or "Is this an April Fool's joke?", consider that the healthcare industry still uses faxes frequently.

I once interviewed at a company that was building software for ordering durable medical equipment in hospitals. They told me that all orders were faxed to the insurance companies, and the error rate for copying data to the faxed form was about 90%. This results in repeated fax transmissions and patients waiting days to know whether their insurance company will buy them a wheelchair.

Using an API like this, you can at least digitize one end of the process, error-free, and still deliver the expected fax to the other side which hasn't upgraded yet.

Re: Programmable Fax – API for sending and receiving faxes

#77

This is neat! But I have to expose the PDF to the internet for Twilio to pick up the file and send it? https://www.twilio.com/docs/api/fax/quickstart#send-a-fax

https://www.twilio.com/docs/api/security#validating-requests

Twilio cryptographically signs its requests

Not sure on the specifics of a GET vs the normal POST callbacks but they definitely are aware this is an issue.

Re: Programmable Fax – API for sending and receiving faxes

#78

Anyone see anything about how they handle simultaneous incoming faxes to the same number? With other faxing APIs we've used, if we get a new inbound fax while another is being received, the second (new) inbound fax will get a busy signal and not get procewsed. Phaxio has said they can handle any number of simultaneous inbound faxes, but we haven't had a chance to try them yet. It would be nice to know if Twilio is an…

Multiple simultaneous incoming is fine. They'll all get received properly.

Re: Programmable Fax – API for sending and receiving faxes

#79

Earlier quoted context omitted.

I think a faxed signature counts as a "wet" signature. Also it's easier to sign then feed into a fax machine than: - sign - scan (usually sent as a weird filename to your corporate email) - save the attachment, rename the file, create a new email, attach the file, send

That's why we have DocuSign!

"Wet signature" being a term with some legal standing. DocuSign, not so much, other than for preliminary real estate actions.

Re: Programmable Fax – API for sending and receiving faxes

#80

Earlier quoted context omitted.

Phaxio founder here. Our pricing might seem higher (and may be in certain situations), but it works a bit differently that Twilio's. Twilio charges you the 1c _plus_ the costs of the call. Phaxio is an "all in" rate _including_ retrying the call. And, at Phaxio, if the calls all fail there's no cost to you. I'm not saying that we won't adjust our pricing (#competition), but there's a difference in the actual unit cos…

How long does it take to send a page of fax? Their pricing is 0.007 per minute. I haven't seen many fax machines take more than a minute per page, but they would have to take 10 minutes to catch up to your pricing. Edit: Fixed time to comparable pricing.

I'd be surprised to see more than a couple minutes for even a complicated fax page. I've seen 45-70 seconds average for a not-too-complicated page.

It also depends on the baud rate (never thought that term would come back, eh?) negotiated between both ends. A 14400 baud transmission will of course be faster than 9600.

Post reply on HN