Context.IO provides API access to core resources in IMAP-enabled mailboxes such as messages, contacts, threads and attachments, and provides webhooks to manage all of these. Apps can be notified of specific content as it arrives, instead of constantly polling a mailbox for matching content. Makes development of apps that look for and push important messages much much easier. http://context.io/docs/2.0/accounts/webhooks
Full disclosure, I do Community Management/Developer Relations for Context.IO.
Brilliant! I've been a beta tester for a while, and my first "broadcast" request on Facebook got me several leads! People really DO want to help out, and putting out a general request is such an easy way to get people almost asking YOU if they can care for your pet! Go Spotwag. Can't wait to see where this'll go!
Not sure how this counts as bait? It's coverage of the announcement, and naturally that was also covered on our company blog? We do have a free offer, listed on our pricing page: http://context.io/pricing
Check out this post about some of the WebHooks we've integrated in v2.0 of the Context.IO email API. No more need to constantly poll our API for relevant messages for your app. Get automatically notified when messages meet your app's criteria.
Have you thought of using Context.IO to eliminate the need for end users to CC My Inbox Assistant at all? IMAP enabled mailboxes can have My Inbox Assistant run in the background without any need for CCIng/BCCing. Take a look at our docs at http://context.io/docs/2.0/, specifically the messages calls: http://context.io/docs/2.0/accounts/messages
Hey guys, it's Sarah-Jane, Community Manager at Context.IO. Yup, you got it. We don't host dedicated mailboxes that your application can receive and send emails from, but since we make the contents of any IMAP account available to your app, whatever is received in that account is like your app receiving it. For the sending part, we're leaving that to Mailgun and other services that focus on this.