My killer app for this needs webhooks, or some sort of event notification when mail arrives. Bonus points for making that condition a stored procedure/filter. Until then I'll probably run out of "quota units" polling the thing..
Gmail API
111–120 of 147 posts
Re: Gmail API
#112Earlier quoted context omitted.
Granularity is the key here. I run a small self-tracking service (zenobase.com), and would love to let my users pull in some "metadata" from their email (e.g. the number of messages in the inbox, or the number of messages sent by hour). But I don't want my users to trust me with unrestricted access to their email.
A meta data only permission would be cool. Access to from, to, cc, date, labels, etc for all mails but no access to the actual content would be good.
Re: Gmail API
#113We (Streak, YCS11) have been using this API for a few days to build our email snoozing feature ( https://www.streak.com/email-snooze-in-gmail ). The API is really nice to use and makes interacting with Gmail way easier relative to IMAP. I'm surprised they don't recommend using this API to build full email clients. I fully expected that to be one of the core use cases. The reason its hard (currently) to build a mail c…
If anyone wants to snooze email without auth'ing your Gmail account, here's one I built in 2008 that's still going strong. http://hitmelater.com/ It costs $30/yr for the high-end service but send me a note and I'll give you a link to signup for free.
Free to use: http://www.pfalke.com Open source: https://github.com/pfalke/returnx
Re: Gmail API
#114Sadly, the API doesn't support search, which makes it extremely limited for all but trivial apps.
EDIT: see https://developers.google.com/gmail/api/v1/reference/users/t... and look at the 'q' parameter
Re: Gmail API
#115Re: Gmail API
#116We (Streak, YCS11) have been using this API for a few days to build our email snoozing feature ( https://www.streak.com/email-snooze-in-gmail ). The API is really nice to use and makes interacting with Gmail way easier relative to IMAP. I'm surprised they don't recommend using this API to build full email clients. I fully expected that to be one of the core use cases. The reason its hard (currently) to build a mail c…
Re: Gmail API
#117I like the idea of opening gmail up to developers via a public API, but I don't like that it comes at the cost of removing support for an open standard like IMAP. I'm worried that API access could be cut back or eliminated entirely in the future depending on developer uptake, leaving gmail entirely inaccessible to third-party applications. Edit: I'm going off of this sentence: >It will replace IMAP, a common but comp…
TBH, I've never understood why more people didn't explore the multipart content type feature of email to extend email. It's typical to have plaintext and html in the same email, but why no JSON using a well defined and published JSON-schema.
Re: Gmail API
#118It'd be interesting to see what kind of limits (no. of calls, concurrency etc.) that Google has put on the API. Has anyone trying this out hit of any of these issues yet?