Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Robert from Email Yak here.

Keep things simple for the devs: That's why we chose to put the API key in the URL, for easy authentication, and stick with just GET and POST request with absolutely no headers required on requests.

It may not be the most RESTful API in existence, but I get alot of emails saying that is sure is an easy API to work with.

MIME's? Seriously? Give me a break. I just want to send and receive email, I don't care how it is made! Email Yak doesn't ask for MIME's and doesn't provide them, just send and receive in plain text or html. Easy.

Even the control panel is minimalistic. Few screens. Just keeping it simple.

Focus on receiving email: Receiving email is one of those programmer white whales, it looks alot easier than it actually is. We chose this task to focus on to make it as easy as possible for devs.

ParsedData: We split each reply in the email thread. That makes it easy to work with the most-recent reply or any individual one.

Sandbox Playground: You can do everything from the UI that you can from the API. So you can see the exact request you need to send to the API and the responses you will get back.

No POP / IMAP: Again, we want to do one thing well and keep things simple, so no need to muddy the waters with these protocols.

If you guys have any questions, shoot me an email at robert@emailyak.com



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: