4 comments

[ 10.8 ms ] story [ 20.5 ms ] thread
What value does this provide on top postageapp's api? I have to imagine most companies would (read:should) standardize on one provider.
I'm not the author of EmailJS but it doesn't require any backend where as PostageApp does.
Backend on top of the existing API? I must be missing something but I still don't understand how this is easier than just hitting the PostageApp or [insert competitor here] API directly.
Hey Matt, I'm one of the founders. All existing APIs require using a secret key, which you obviously wouldn't want to share in your front-end code. We overcome this by allowing sending only predefined templates, so for a "Share with a friend" feature you'd create a template called "share", and your call would look like -

  EmailJS.send("share",{"to": "friend@gmail.com","message":"You have to check this out!"})
This should prevent using our service for spamming, and we'll also offer some tools like CAPTCHA image, or rate limiting, to deal with spam/abuse.

Let me know if you have any further questions!