Sure. You could use plus+addressing to identify the individual post or you could register an address that was specific for that post. Email Yak lets you call Register Address (http://docs.emailyak.com/register-address.html) to create as many email addresses as you want.
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
Hey HN, I'm a longtime reader and this is my first Show HN (exciting!) It's a collaboration between me and two friends, and we're building this upon another app we made called EmailYak, an API to receive email. We're trying something new and releasing the documentation to an app while we're still building it.
We'd love feedback. Do you belong to any of these categories?
1) You've built an app with two distinct groups of users (say, people with cars and those looking for a ride) and they were able to communicate with each other. Did you expose personal email addresses? Did you send notification emails that people could reply to directly in their inbox? Or were they only able to read and reply to messages on your site?
2) You built an app where you wished users could message each other but didn't add that feature. What stopped you? Did you try to parse incoming email? What tools or APIs did you try out?
If you note which group(s) above you belong to in your comment that'd be great :)
All plans have unlimited emil addresses included.