TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Gmail API

528 点作者 elie_CH将近 11 年前

32 条评论

alooPotato将近 11 年前
We (Streak, YCS11) have been using this API for a few days to build our email snoozing feature (<a href="https://www.streak.com/email-snooze-in-gmail" rel="nofollow">https:&#x2F;&#x2F;www.streak.com&#x2F;email-snooze-in-gmail</a>).<p>The API is really nice to use and makes interacting with Gmail way easier relative to IMAP. I&#x27;m surprised they don&#x27;t recommend using this API to build full email clients. I fully expected that to be one of the core use cases.<p>The reason its hard (currently) to build a mail client using the API is that call to list the threads in your inbox or any other label doesn&#x27;t actually return the messages in those threads. So its hard to show the people that are on the thread as well as some of the timestamp. If they added some more summary data to the thread object, I could see this becoming feasible.
评论 #7946747 未加载
评论 #7946986 未加载
评论 #7946785 未加载
评论 #7947674 未加载
评论 #7948645 未加载
评论 #7946298 未加载
评论 #7948082 未加载
评论 #7947184 未加载
评论 #7946363 未加载
评论 #7947717 未加载
评论 #7949217 未加载
bpodgursky将近 11 年前
I like the idea of opening gmail up to developers via a public API, but I don&#x27;t like that it comes at the cost of removing support for an open standard like IMAP. I&#x27;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.<p>Edit: I&#x27;m going off of this sentence:<p>&gt;It will replace IMAP, a common but complex way for applications to communicate with most email services, limiting the number of apps that can work with Gmail<p>Maybe it&#x27;s misleading, but it sounds like the plan is to drop support.
评论 #7946608 未加载
评论 #7946069 未加载
评论 #7946438 未加载
评论 #7946626 未加载
评论 #7946530 未加载
评论 #7946498 未加载
评论 #7946062 未加载
评论 #7946094 未加载
ejain将近 11 年前
Nice, but I&#x27;m very reluctant to give any third-party access to my mailbox. Most sites I use let me reset my password by email, so this is like handing over the keys to the castle.
评论 #7946366 未加载
评论 #7946483 未加载
评论 #7946708 未加载
xienze将近 11 年前
I can&#x27;t believe how many people are stoked about this. If you look at <a href="https://developers.google.com/gmail/api/auth/scopes" rel="nofollow">https:&#x2F;&#x2F;developers.google.com&#x2F;gmail&#x2F;api&#x2F;auth&#x2F;scopes</a>, basically apps can do a combination of a) have full control, b) read everything, c) do everything but delete emails, or d) read&#x2F;write&#x2F;send drafts.<p>Granting that level of access with no fine-grained control to 3rd party apps seems insane to me. I predict at least a couple major security incidents in the future.
评论 #7946754 未加载
评论 #7946761 未加载
评论 #7946667 未加载
chimeracoder将近 11 年前
I&#x27;m not sure what this API enables that can&#x27;t be done over IMAP. IMAP may not be as familiar as JSON-over-REST, but it&#x27;s supported by virtually all mail clients and providers, which makes it about as open as you can get.<p>Already the Gmail IMAP implementation is non-standard in a number of annoying-but-workable ways. I&#x27;ve been suspecting for a while that they&#x27;re going to kill it or lock it down, the way they did for XMPP and Talk[0]. I really hope this isn&#x27;t the first step towards that.<p>As bpodgursky pointed out, this sentence is troubling:<p>&gt; It will <i>replace</i> IMAP, a common but complex way for applications to communicate with most email services, <i>limiting the number of apps that can work with Gmail</i><p>Emphasis mine.<p>[0] I admittedly had no evidence for this speculation before today, just a worry.
评论 #7946925 未加载
评论 #7946849 未加载
jonathonf将近 11 年前
Two key bits from the first two paragraphs of the article:<p>&quot;make it easier for other Internet applications to use information in your email&quot;<p>&quot;It will replace IMAP&quot;<p>First one seems par for the course, the second one doesn&#x27;t seem to be reflected in the Google blog post [1]. Certainly for the moment, thankfully, it looks like IMAP is staying:<p>&quot;The Gmail API should not be used to replace IMAP for full-fledged email client access&quot; [2]<p>[1] <a href="http://googleappsdeveloper.blogspot.com/2014/06/introducing-new-gmail-api.html" rel="nofollow">http:&#x2F;&#x2F;googleappsdeveloper.blogspot.com&#x2F;2014&#x2F;06&#x2F;introducing-...</a> [2] <a href="https://developers.google.com/gmail/api/" rel="nofollow">https:&#x2F;&#x2F;developers.google.com&#x2F;gmail&#x2F;api&#x2F;</a>
jobu将近 11 年前
It would take something pretty amazing for me to allow anyone access to my gmail account. LinkedIn definitely made me skeptical on allowing even trustworthy-seeming companies access to my contacts.
评论 #7947071 未加载
评论 #7947488 未加载
cliveowen将近 11 年前
This might be big, I was just done complaining about the user interface of the GMail web app. If this means that developers can now effectively create another interface on top of a real GMail API this has the potential to really change things. I can already envision several ways in how I could improve my inbox management and reduce the time spent sifting through emails.
评论 #7946077 未加载
评论 #7946190 未加载
mik3y将近 11 年前
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&#x2F;filter.<p>Until then I&#x27;ll probably run out of &quot;quota units&quot; polling the thing..
评论 #7946459 未加载
评论 #7949396 未加载
评论 #7947910 未加载
评论 #7948797 未加载
评论 #7947077 未加载
评论 #7946596 未加载
mp3jeep01将近 11 年前
If they can combine this ease of accessibility for developers with a security model on the end-user side, I think it can be a solid win.<p>I&#x27;d love to see granularity in what the API can access, for example, TripIt may request something like &quot;Grant access to emails from the domain travelocity.com, usairways.com, etc.,&quot; and I can know with confidence that they will not have access to the rest of my inbox.
评论 #7946521 未加载
roma1n将近 11 年前
It&#x27;s high time that we get user-controlled sandboxes that could enforce additional security restrictions and are application-transparent. If a third party app requires access (R&#x2F;W) to my Google Drive files, I should be able to limit said access to a single folder, for instance, and any other content should simply be invisible to it. These restrictions should be tuneable at any time (before and after app install) and there should be visualization tools to control their effectiveness.
milankragujevic将近 11 年前
I find it funny that they aren&#x27;t using a Chromebook and Nexus 5 and the Nexus 7 as the product examples but instead iPhone and Macbook and iPad.
vijayaggarwal将近 11 年前
Google has been adding lots of <i>widgets</i> to email recently, like RSVP on invitations, itinerary on flight booking emails, etc. These are pretty useful features and I believe a lot more are possible with the APIs being opened.<p>However, I feel the access control is very coarse grained. For example, RSVP widget needs access to only event related emails and itinerary needs only travel booking emails, but the API spec does not allow for such fine grained control.<p>IMO, given that google is able bucket-ize emails into travel booking, event, etc., and even user-defined labels for any custom grouping, allowing access on such buckets would be nearly as useful and much more user-privacy friendly. For example, an accounting app could still access invoices from my inbox to update my accounts automatically. Google could even push for microformats kind of annotation to make emails semantically richer.
评论 #7946370 未加载
jimm将近 11 年前
Can&#x27;t wait for the Emacs Lisp client library! (Wish I had time to work on that.)
nirajr将近 11 年前
We (<a href="http://grexit.com" rel="nofollow">http:&#x2F;&#x2F;grexit.com</a>) let users share Gmail labels. We&#x27;re very happy to see this release as it has been a pain to build and scale our service over IMAP.<p>It&#x27;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?
roxtar将近 11 年前
This raises serious privacy concerns for me.<p>Technical users can and will block access to portions of the API during authenticatcaion, but what about people like my parents? They might very well login, giving full permissions to the app, seeing that it&#x27;s a trusted google URL while not knowing what they have done.<p>This is going to open a new can of worms.
essenobi将近 11 年前
I see that as being a great opportunity for customer referrals. So many people have a gmail account. It&#x27;d be cool, from the business&#x27; standpoint, to see if your customers are connected through something as simple as email if they allow an app to access sender information.
epaulson将近 11 年前
This is fantastic. What we need next are OAuth libraries for Postfix and other SMTP servers, so I can use Gmail to centralize and read my email but still use my home organization&#x27;s SMTP server to send email, without having to give Google a copy of my password.
nnnnni将近 11 年前
This looks like it&#x27;d be EXTREMELY useful for cronjobs and other things where you need to send email to yourself (or another address) automatically. It would remove the need to self-host email just so that you can send status reports...
jakozaur将近 11 年前
Great idea. I only wish it was an open standard... Email success b&#x2F;c of it openness, but if we start proprietary APIs on top of it then we are getting locked in.
bgentry将近 11 年前
My only question: can you use these APIs to mute threads? That&#x27;s the one major Gmail feature that could never be done with IMAP.
niutech将近 11 年前
Wy don&#x27;t they make an open standard RESTful API which would be used across mail providers, just like IMAP?
zak_mc_kracken将近 11 年前
Sadly, the API doesn&#x27;t support search, which makes it extremely limited for all but trivial apps.
评论 #7947957 未加载
donniezazen将近 11 年前
Does this help with getting the new Gmail Inbox in the IMAP clients?
anonfunction将近 11 年前
The API Overview link is dead. I expect better.
coherentpony将近 11 年前
GMail desktop client? Yes please :)
评论 #7946907 未加载
评论 #7946910 未加载
azncliff将近 11 年前
How do you add google-api-services-gmail-v1-[version].jar to your classpath?? Where is this file?
Dorian-Marie将近 11 年前
Here is the actual Google blog post: <a href="http://googleappsdeveloper.blogspot.com.ar/2014/06/introducing-new-gmail-api.html" rel="nofollow">http:&#x2F;&#x2F;googleappsdeveloper.blogspot.com.ar&#x2F;2014&#x2F;06&#x2F;introduci...</a>
hafichuk将近 11 年前
The article is light on the technical details. Here&#x27;s the API: <a href="https://developers.google.com/gmail/api/" rel="nofollow">https:&#x2F;&#x2F;developers.google.com&#x2F;gmail&#x2F;api&#x2F;</a>
dang将近 11 年前
We changed the url from <a href="http://online.wsj.com/news/article_email/google-opens-gmail-making-it-more-of-a-platform-for-developers-1403719202-lMyQjAxMTA0MDIwNTEyNDUyWj" rel="nofollow">http:&#x2F;&#x2F;online.wsj.com&#x2F;news&#x2F;article_email&#x2F;google-opens-gmail-...</a>.
jusben1369将近 11 年前
Was I the only one who thought for a moment this was another privacy related story (opening my email!)
评论 #7946108 未加载
joedevon将近 11 年前
Hot off the presses! Google just released the latest future ex-api they will get bored of in a couple&#x2F;few years and kill, along with any company that depends on it. #rememberthiscommentthen