gmail-api

According to the Gmail API reference , Users.messages: list "[lists] the messages in the user's mailbox". In my observation, the messages are returned in descending order by data. Is this a correct assumption? Basically I want to be able to process a user's inbox after a couple of days without reprocessing messages I have already processed. I would do that by stopping once I stumble upon an email I have seen before. Using the history doesn't work reliable, since it is documented that history might expire within a few hours, requiring a full new sync. Yes, you are correct. Messages are returned

I've been using Indy under Delphi to send message via a gmail account, using the TIdSMTP and TIdMessage components. This works absolutely fine. However, my client has requested to save the message to the DRAFTS folder to allow him to make changes to the (programatically created) message before actually sending it. GMail API is supposed to support this, but the provided examples are not in Delphi/Indy formats... I'm looking for minimal programming changes so I'd like to know if it is possible in the Indy components too? TIdMessage allows for a "mfDraft" flag, but this doesn't prevent the

The new Gmail API allows us to create and view drafts, but is there a way to get a URL link to view the draft? I can manually create the link using the draft's ThreadId with something like this: https://mail.google.com/mail/u/0/#drafts?compose= {ThreadId} But that is somewhat fragile if Google decides to change how those URLs are structured. I also don't know if the URL will be different for people in other countries. The 0 will also change depending on how many accounts you are logged into in the browser. Is there a better way to get this link than creating it manually like I am? Also, is

I am trying to read the gmail mail message, using gmail api, and after reading the mail, I am removing the message label, so that I don't need to process it again. I am able to read the mail successfully, but when I am trying to modify the message Label ( service.Users.Messages.Modify(mods, userId, messageId).Execute(); ) then I am getting the error message: An error occurred: Google.Apis.Requests.RequestError Insufficient Permission [403] Errors [ Message[Insufficient Permission] Location[ - ] Reason[insufficientPermis sions] Domain[global]> ]. I am not able to figure out, what may have gone

While fiddling with the Gmail API, I noticed that if I don't use any filters, the Users.messages: list method also returns messages sent and received through Google Hangout or Gmail Chat. Which is very nice. The json object for a Hangout message is structured like an email (with payload, headers etc), but the only header provided is the sender. There's no information about the time the message is sent. I've looked through all other Gmail API methods (threads, history...) but none of them provides datetime information for chat messages. Any idea if/how I could lookup a timestamp for chat

We are building a service that utilizes the Gmail API. In order to understand our costs as we scale, I would like to know how much it costs to use the Gmail API. I've followed the instructions at https://developers.google.com/gmail/api/v1/reference/quota through to the point at which it says: If you have enabled billing for your project [we have], clicking Quota takes you to a page where you can view and change quota-related settings. The only option on that page for changing our daily quota is to "Apply for higher quota"; however, clicking that opens a window that says: Please be sure to

I'm having some trouble sending a message to multiple addresses using the Gmail API. I've successfully sent a message to only one address, but get the following error when I include multiple comma-separated addresses in the 'To' field: An error occurred: https://www.googleapis.com/gmail/v1/users/me/messages/send?alt=json returned "Invalid to header"> I'm using the CreateMessage and SendMessage methods from this Gmail API guide: https://developers.google.com/gmail/api/guides/sending That guide states that the Gmail API requires messages that are RFC-2822 compliant. I again didn't have much luck