How do you prevent email/web filtering applications that "scan" email/web URLs from triggering the confirmation/denials?
Show HN: ApproveAPI – Real-Time user approvals via email, SMS, and push
11–20 of 58 posts
Re: Show HN: ApproveAPI – Real-Time user approvals via email, SMS, and push
#12Wow, $1 for 100 emails is very very very very expensive. So expensive that I'd opt to build this in house rather and take on the costs associated with it and still come out saving money. It's a pretty solid idea otherwise.
Curious how you calculated that -- mind sharing back of the napkin?
The price is right there on the page? $1 for 100 approvals (additional SMS cost not included)
Re: Show HN: ApproveAPI – Real-Time user approvals via email, SMS, and push
#13Wow, $1 for 100 emails is very very very very expensive. So expensive that I'd opt to build this in house rather and take on the costs associated with it and still come out saving money. It's a pretty solid idea otherwise.
> I'd opt to build this in house rather and take on the costs associated with it and still come out saving money
This seems to be the default position of almost everyone in IT, everywhere I go. People make this claim without doing any calculations.
I can imagine building this in house would be at least a few weeks of developer work and some more devops. That's tens of thousands of dollars. You'd have to send a million emails to break even. How many of this kind of transactional email do you send per year?
Re: Show HN: ApproveAPI – Real-Time user approvals via email, SMS, and push
#14Wow, $1 for 100 emails is very very very very expensive. So expensive that I'd opt to build this in house rather and take on the costs associated with it and still come out saving money. It's a pretty solid idea otherwise.
Hey -- one of the creators here, thanks for your comment. We definitely don't want to price out companies from using our service so we are listening carefully.
I also want to mention that we do support volume pricing, so if you want to send lots of approvals per month we can work together on a price that makes sense for your use case -- just reach out to us at support@approveapi.com.
Re: Show HN: ApproveAPI – Real-Time user approvals via email, SMS, and push
#15The OpenAPI link is returning a 404. https://approveapi.com/docs/open-api-spec-2.0.json
Re: Show HN: ApproveAPI – Real-Time user approvals via email, SMS, and push
#16The OpenAPI link is returning a 404. https://approveapi.com/docs/open-api-spec-2.0.json
Oops that's an outdated link, will fix asap. In the mean-time here is the spec: https://github.com/approveapi/openapi-spec
Re: Show HN: ApproveAPI – Real-Time user approvals via email, SMS, and push
#17A useful feature for a service like this is being able to set delegates both from the producer and consumer side. For example, if the person I sent the notification to doesn’t respond in , then send a request to this person (potentially their manager / emergency contact / etc...) . And, as someone receiving notifications, set another person as my delegate for a certain time window and for a specific application. This is what we have to deal with to handle OOO scenarios.
Re: Show HN: ApproveAPI – Real-Time user approvals via email, SMS, and push
#18Wow, $1 for 100 emails is very very very very expensive. So expensive that I'd opt to build this in house rather and take on the costs associated with it and still come out saving money. It's a pretty solid idea otherwise.
> I'd opt to build this in house rather and take on the costs associated with it and still come out saving money This seems to be the default position of almost everyone in IT, everywhere I go. People make this claim without doing any calculations. I can imagine building this in house would be at least a few weeks of developer work and some more devops. That's tens of thousands of dollars. You'd have to send a millio…
It's a crazy calculation. For mass marketing it'd be outrageous. But for mission-critical business flows? It's a rounding error.
Re: Show HN: ApproveAPI – Real-Time user approvals via email, SMS, and push
#19Wow, $1 for 100 emails is very very very very expensive. So expensive that I'd opt to build this in house rather and take on the costs associated with it and still come out saving money. It's a pretty solid idea otherwise.
> I'd opt to build this in house rather and take on the costs associated with it and still come out saving money This seems to be the default position of almost everyone in IT, everywhere I go. People make this claim without doing any calculations. I can imagine building this in house would be at least a few weeks of developer work and some more devops. That's tens of thousands of dollars. You'd have to send a millio…
> This seems to be the default position of almost everyone in IT, everywhere I go. People make this claim without doing any calculations.
I constantly see people not even considering what it means to be giving (potentially critical) business processes away to another company, not having any real knowledge in house, and not realizing that sometimes partners suck and won't help you fix problems in their software.
Neither is a sure bet all of the time, but just dismissing pulling things in house neglects a lot of other downsides to outsourcing.