chore: update docs/dyn (#1106)
diff --git a/docs/dyn/gmail_v1.users.drafts.html b/docs/dyn/gmail_v1.users.drafts.html
index 9972e88..5fab3ec 100644
--- a/docs/dyn/gmail_v1.users.drafts.html
+++ b/docs/dyn/gmail_v1.users.drafts.html
@@ -87,7 +87,7 @@
<code><a href="#get">get(userId, id, format=None, x__xgafv=None)</a></code></p>
<p class="firstline">Gets the specified draft.</p>
<p class="toc_element">
- <code><a href="#list">list(userId, includeSpamTrash=None, pageToken=None, q=None, maxResults=None, x__xgafv=None)</a></code></p>
+ <code><a href="#list">list(userId, maxResults=None, q=None, includeSpamTrash=None, pageToken=None, x__xgafv=None)</a></code></p>
<p class="firstline">Lists the drafts in the user's mailbox.</p>
<p class="toc_element">
<code><a href="#list_next">list_next(previous_request, previous_response)</a></code></p>
@@ -114,39 +114,39 @@
The object takes the form of:
{ # A draft email in the user's mailbox.
- "id": "A String", # The immutable ID of the draft.
- "message": { # An email message. # The message content of the draft.
- "internalDate": "A String", # The internal message creation timestamp (epoch ms), which determines ordering in the inbox. For normal SMTP-received email, this represents the time the message was originally accepted by Google, which is more reliable than the `Date` header. However, for API-migrated mail, it can be configured by client to be based on the `Date` header.
- "id": "A String", # The immutable ID of the message.
- "sizeEstimate": 42, # Estimated size in bytes of the message.
- "threadId": "A String", # The ID of the thread the message belongs to. To add a message or draft to a thread, the following criteria must be met: 1. The requested `threadId` must be specified on the `Message` or `Draft.Message` you supply with your request. 2. The `References` and `In-Reply-To` headers must be set in compliance with the [RFC 2822](https://tools.ietf.org/html/rfc2822) standard. 3. The `Subject` headers must match.
- "snippet": "A String", # A short part of the message text.
- "labelIds": [ # List of IDs of labels applied to this message.
- "A String",
- ],
- "historyId": "A String", # The ID of the last history record that modified this message.
- "payload": { # A single MIME message part. # The parsed email structure in the message parts.
- "parts": [ # The child MIME message parts of this part. This only applies to container MIME message parts, for example `multipart/*`. For non- container MIME message part types, such as `text/plain`, this field is empty. For more information, see RFC 1521.
- # Object with schema name: MessagePart
- ],
- "headers": [ # List of headers on this message part. For the top-level message part, representing the entire message payload, it will contain the standard RFC 2822 email headers such as `To`, `From`, and `Subject`.
- {
- "value": "A String", # The value of the header after the `:` separator. For example, `someuser@example.com`.
- "name": "A String", # The name of the header before the `:` separator. For example, `To`.
+ "message": { # An email message. # The message content of the draft.
+ "historyId": "A String", # The ID of the last history record that modified this message.
+ "payload": { # A single MIME message part. # The parsed email structure in the message parts.
+ "parts": [ # The child MIME message parts of this part. This only applies to container MIME message parts, for example `multipart/*`. For non- container MIME message part types, such as `text/plain`, this field is empty. For more information, see RFC 1521.
+ # Object with schema name: MessagePart
+ ],
+ "mimeType": "A String", # The MIME type of the message part.
+ "partId": "A String", # The immutable ID of the message part.
+ "filename": "A String", # The filename of the attachment. Only present if this message part represents an attachment.
+ "headers": [ # List of headers on this message part. For the top-level message part, representing the entire message payload, it will contain the standard RFC 2822 email headers such as `To`, `From`, and `Subject`.
+ {
+ "value": "A String", # The value of the header after the `:` separator. For example, `someuser@example.com`.
+ "name": "A String", # The name of the header before the `:` separator. For example, `To`.
+ },
+ ],
+ "body": { # The body of a single MIME message part. # The message part body for this part, which may be empty for container MIME message parts.
+ "data": "A String", # The body data of a MIME message part as a base64url encoded string. May be empty for MIME container types that have no message body or when the body data is sent as a separate attachment. An attachment ID is present if the body data is contained in a separate attachment.
+ "size": 42, # Number of bytes for the message part data (encoding notwithstanding).
+ "attachmentId": "A String", # When present, contains the ID of an external attachment that can be retrieved in a separate `messages.attachments.get` request. When not present, the entire content of the message part body is contained in the data field.
},
- ],
- "partId": "A String", # The immutable ID of the message part.
- "mimeType": "A String", # The MIME type of the message part.
- "filename": "A String", # The filename of the attachment. Only present if this message part represents an attachment.
- "body": { # The body of a single MIME message part. # The message part body for this part, which may be empty for container MIME message parts.
- "data": "A String", # The body data of a MIME message part as a base64url encoded string. May be empty for MIME container types that have no message body or when the body data is sent as a separate attachment. An attachment ID is present if the body data is contained in a separate attachment.
- "attachmentId": "A String", # When present, contains the ID of an external attachment that can be retrieved in a separate `messages.attachments.get` request. When not present, the entire content of the message part body is contained in the data field.
- "size": 42, # Number of bytes for the message part data (encoding notwithstanding).
},
+ "labelIds": [ # List of IDs of labels applied to this message.
+ "A String",
+ ],
+ "internalDate": "A String", # The internal message creation timestamp (epoch ms), which determines ordering in the inbox. For normal SMTP-received email, this represents the time the message was originally accepted by Google, which is more reliable than the `Date` header. However, for API-migrated mail, it can be configured by client to be based on the `Date` header.
+ "id": "A String", # The immutable ID of the message.
+ "sizeEstimate": 42, # Estimated size in bytes of the message.
+ "raw": "A String", # The entire email message in an RFC 2822 formatted and base64url encoded string. Returned in `messages.get` and `drafts.get` responses when the `format=RAW` parameter is supplied.
+ "snippet": "A String", # A short part of the message text.
+ "threadId": "A String", # The ID of the thread the message belongs to. To add a message or draft to a thread, the following criteria must be met: 1. The requested `threadId` must be specified on the `Message` or `Draft.Message` you supply with your request. 2. The `References` and `In-Reply-To` headers must be set in compliance with the [RFC 2822](https://tools.ietf.org/html/rfc2822) standard. 3. The `Subject` headers must match.
},
- "raw": "A String", # The entire email message in an RFC 2822 formatted and base64url encoded string. Returned in `messages.get` and `drafts.get` responses when the `format=RAW` parameter is supplied.
- },
-}
+ "id": "A String", # The immutable ID of the draft.
+ }
x__xgafv: string, V1 error format.
Allowed values
@@ -159,39 +159,39 @@
An object of the form:
{ # A draft email in the user's mailbox.
- "id": "A String", # The immutable ID of the draft.
- "message": { # An email message. # The message content of the draft.
- "internalDate": "A String", # The internal message creation timestamp (epoch ms), which determines ordering in the inbox. For normal SMTP-received email, this represents the time the message was originally accepted by Google, which is more reliable than the `Date` header. However, for API-migrated mail, it can be configured by client to be based on the `Date` header.
- "id": "A String", # The immutable ID of the message.
- "sizeEstimate": 42, # Estimated size in bytes of the message.
- "threadId": "A String", # The ID of the thread the message belongs to. To add a message or draft to a thread, the following criteria must be met: 1. The requested `threadId` must be specified on the `Message` or `Draft.Message` you supply with your request. 2. The `References` and `In-Reply-To` headers must be set in compliance with the [RFC 2822](https://tools.ietf.org/html/rfc2822) standard. 3. The `Subject` headers must match.
- "snippet": "A String", # A short part of the message text.
- "labelIds": [ # List of IDs of labels applied to this message.
- "A String",
- ],
- "historyId": "A String", # The ID of the last history record that modified this message.
- "payload": { # A single MIME message part. # The parsed email structure in the message parts.
- "parts": [ # The child MIME message parts of this part. This only applies to container MIME message parts, for example `multipart/*`. For non- container MIME message part types, such as `text/plain`, this field is empty. For more information, see RFC 1521.
- # Object with schema name: MessagePart
- ],
- "headers": [ # List of headers on this message part. For the top-level message part, representing the entire message payload, it will contain the standard RFC 2822 email headers such as `To`, `From`, and `Subject`.
- {
- "value": "A String", # The value of the header after the `:` separator. For example, `someuser@example.com`.
- "name": "A String", # The name of the header before the `:` separator. For example, `To`.
+ "message": { # An email message. # The message content of the draft.
+ "historyId": "A String", # The ID of the last history record that modified this message.
+ "payload": { # A single MIME message part. # The parsed email structure in the message parts.
+ "parts": [ # The child MIME message parts of this part. This only applies to container MIME message parts, for example `multipart/*`. For non- container MIME message part types, such as `text/plain`, this field is empty. For more information, see RFC 1521.
+ # Object with schema name: MessagePart
+ ],
+ "mimeType": "A String", # The MIME type of the message part.
+ "partId": "A String", # The immutable ID of the message part.
+ "filename": "A String", # The filename of the attachment. Only present if this message part represents an attachment.
+ "headers": [ # List of headers on this message part. For the top-level message part, representing the entire message payload, it will contain the standard RFC 2822 email headers such as `To`, `From`, and `Subject`.
+ {
+ "value": "A String", # The value of the header after the `:` separator. For example, `someuser@example.com`.
+ "name": "A String", # The name of the header before the `:` separator. For example, `To`.
+ },
+ ],
+ "body": { # The body of a single MIME message part. # The message part body for this part, which may be empty for container MIME message parts.
+ "data": "A String", # The body data of a MIME message part as a base64url encoded string. May be empty for MIME container types that have no message body or when the body data is sent as a separate attachment. An attachment ID is present if the body data is contained in a separate attachment.
+ "size": 42, # Number of bytes for the message part data (encoding notwithstanding).
+ "attachmentId": "A String", # When present, contains the ID of an external attachment that can be retrieved in a separate `messages.attachments.get` request. When not present, the entire content of the message part body is contained in the data field.
},
- ],
- "partId": "A String", # The immutable ID of the message part.
- "mimeType": "A String", # The MIME type of the message part.
- "filename": "A String", # The filename of the attachment. Only present if this message part represents an attachment.
- "body": { # The body of a single MIME message part. # The message part body for this part, which may be empty for container MIME message parts.
- "data": "A String", # The body data of a MIME message part as a base64url encoded string. May be empty for MIME container types that have no message body or when the body data is sent as a separate attachment. An attachment ID is present if the body data is contained in a separate attachment.
- "attachmentId": "A String", # When present, contains the ID of an external attachment that can be retrieved in a separate `messages.attachments.get` request. When not present, the entire content of the message part body is contained in the data field.
- "size": 42, # Number of bytes for the message part data (encoding notwithstanding).
},
+ "labelIds": [ # List of IDs of labels applied to this message.
+ "A String",
+ ],
+ "internalDate": "A String", # The internal message creation timestamp (epoch ms), which determines ordering in the inbox. For normal SMTP-received email, this represents the time the message was originally accepted by Google, which is more reliable than the `Date` header. However, for API-migrated mail, it can be configured by client to be based on the `Date` header.
+ "id": "A String", # The immutable ID of the message.
+ "sizeEstimate": 42, # Estimated size in bytes of the message.
+ "raw": "A String", # The entire email message in an RFC 2822 formatted and base64url encoded string. Returned in `messages.get` and `drafts.get` responses when the `format=RAW` parameter is supplied.
+ "snippet": "A String", # A short part of the message text.
+ "threadId": "A String", # The ID of the thread the message belongs to. To add a message or draft to a thread, the following criteria must be met: 1. The requested `threadId` must be specified on the `Message` or `Draft.Message` you supply with your request. 2. The `References` and `In-Reply-To` headers must be set in compliance with the [RFC 2822](https://tools.ietf.org/html/rfc2822) standard. 3. The `Subject` headers must match.
},
- "raw": "A String", # The entire email message in an RFC 2822 formatted and base64url encoded string. Returned in `messages.get` and `drafts.get` responses when the `format=RAW` parameter is supplied.
- },
- }</pre>
+ "id": "A String", # The immutable ID of the draft.
+ }</pre>
</div>
<div class="method">
@@ -230,51 +230,51 @@
An object of the form:
{ # A draft email in the user's mailbox.
- "id": "A String", # The immutable ID of the draft.
- "message": { # An email message. # The message content of the draft.
- "internalDate": "A String", # The internal message creation timestamp (epoch ms), which determines ordering in the inbox. For normal SMTP-received email, this represents the time the message was originally accepted by Google, which is more reliable than the `Date` header. However, for API-migrated mail, it can be configured by client to be based on the `Date` header.
- "id": "A String", # The immutable ID of the message.
- "sizeEstimate": 42, # Estimated size in bytes of the message.
- "threadId": "A String", # The ID of the thread the message belongs to. To add a message or draft to a thread, the following criteria must be met: 1. The requested `threadId` must be specified on the `Message` or `Draft.Message` you supply with your request. 2. The `References` and `In-Reply-To` headers must be set in compliance with the [RFC 2822](https://tools.ietf.org/html/rfc2822) standard. 3. The `Subject` headers must match.
- "snippet": "A String", # A short part of the message text.
- "labelIds": [ # List of IDs of labels applied to this message.
- "A String",
- ],
- "historyId": "A String", # The ID of the last history record that modified this message.
- "payload": { # A single MIME message part. # The parsed email structure in the message parts.
- "parts": [ # The child MIME message parts of this part. This only applies to container MIME message parts, for example `multipart/*`. For non- container MIME message part types, such as `text/plain`, this field is empty. For more information, see RFC 1521.
- # Object with schema name: MessagePart
- ],
- "headers": [ # List of headers on this message part. For the top-level message part, representing the entire message payload, it will contain the standard RFC 2822 email headers such as `To`, `From`, and `Subject`.
- {
- "value": "A String", # The value of the header after the `:` separator. For example, `someuser@example.com`.
- "name": "A String", # The name of the header before the `:` separator. For example, `To`.
+ "message": { # An email message. # The message content of the draft.
+ "historyId": "A String", # The ID of the last history record that modified this message.
+ "payload": { # A single MIME message part. # The parsed email structure in the message parts.
+ "parts": [ # The child MIME message parts of this part. This only applies to container MIME message parts, for example `multipart/*`. For non- container MIME message part types, such as `text/plain`, this field is empty. For more information, see RFC 1521.
+ # Object with schema name: MessagePart
+ ],
+ "mimeType": "A String", # The MIME type of the message part.
+ "partId": "A String", # The immutable ID of the message part.
+ "filename": "A String", # The filename of the attachment. Only present if this message part represents an attachment.
+ "headers": [ # List of headers on this message part. For the top-level message part, representing the entire message payload, it will contain the standard RFC 2822 email headers such as `To`, `From`, and `Subject`.
+ {
+ "value": "A String", # The value of the header after the `:` separator. For example, `someuser@example.com`.
+ "name": "A String", # The name of the header before the `:` separator. For example, `To`.
+ },
+ ],
+ "body": { # The body of a single MIME message part. # The message part body for this part, which may be empty for container MIME message parts.
+ "data": "A String", # The body data of a MIME message part as a base64url encoded string. May be empty for MIME container types that have no message body or when the body data is sent as a separate attachment. An attachment ID is present if the body data is contained in a separate attachment.
+ "size": 42, # Number of bytes for the message part data (encoding notwithstanding).
+ "attachmentId": "A String", # When present, contains the ID of an external attachment that can be retrieved in a separate `messages.attachments.get` request. When not present, the entire content of the message part body is contained in the data field.
},
- ],
- "partId": "A String", # The immutable ID of the message part.
- "mimeType": "A String", # The MIME type of the message part.
- "filename": "A String", # The filename of the attachment. Only present if this message part represents an attachment.
- "body": { # The body of a single MIME message part. # The message part body for this part, which may be empty for container MIME message parts.
- "data": "A String", # The body data of a MIME message part as a base64url encoded string. May be empty for MIME container types that have no message body or when the body data is sent as a separate attachment. An attachment ID is present if the body data is contained in a separate attachment.
- "attachmentId": "A String", # When present, contains the ID of an external attachment that can be retrieved in a separate `messages.attachments.get` request. When not present, the entire content of the message part body is contained in the data field.
- "size": 42, # Number of bytes for the message part data (encoding notwithstanding).
},
+ "labelIds": [ # List of IDs of labels applied to this message.
+ "A String",
+ ],
+ "internalDate": "A String", # The internal message creation timestamp (epoch ms), which determines ordering in the inbox. For normal SMTP-received email, this represents the time the message was originally accepted by Google, which is more reliable than the `Date` header. However, for API-migrated mail, it can be configured by client to be based on the `Date` header.
+ "id": "A String", # The immutable ID of the message.
+ "sizeEstimate": 42, # Estimated size in bytes of the message.
+ "raw": "A String", # The entire email message in an RFC 2822 formatted and base64url encoded string. Returned in `messages.get` and `drafts.get` responses when the `format=RAW` parameter is supplied.
+ "snippet": "A String", # A short part of the message text.
+ "threadId": "A String", # The ID of the thread the message belongs to. To add a message or draft to a thread, the following criteria must be met: 1. The requested `threadId` must be specified on the `Message` or `Draft.Message` you supply with your request. 2. The `References` and `In-Reply-To` headers must be set in compliance with the [RFC 2822](https://tools.ietf.org/html/rfc2822) standard. 3. The `Subject` headers must match.
},
- "raw": "A String", # The entire email message in an RFC 2822 formatted and base64url encoded string. Returned in `messages.get` and `drafts.get` responses when the `format=RAW` parameter is supplied.
- },
- }</pre>
+ "id": "A String", # The immutable ID of the draft.
+ }</pre>
</div>
<div class="method">
- <code class="details" id="list">list(userId, includeSpamTrash=None, pageToken=None, q=None, maxResults=None, x__xgafv=None)</code>
+ <code class="details" id="list">list(userId, maxResults=None, q=None, includeSpamTrash=None, pageToken=None, x__xgafv=None)</code>
<pre>Lists the drafts in the user's mailbox.
Args:
userId: string, The user's email address. The special value `me` can be used to indicate the authenticated user. (required)
+ maxResults: integer, Maximum number of drafts to return.
+ q: string, Only return draft messages matching the specified query. Supports the same query format as the Gmail search box. For example, `"from:someuser@example.com rfc822msgid: is:unread"`.
includeSpamTrash: boolean, Include drafts from `SPAM` and `TRASH` in the results.
pageToken: string, Page token to retrieve a specific page of results in the list.
- q: string, Only return draft messages matching the specified query. Supports the same query format as the Gmail search box. For example, `"from:someuser@example.com rfc822msgid: is:unread"`.
- maxResults: integer, Maximum number of drafts to return.
x__xgafv: string, V1 error format.
Allowed values
1 - v1 error format
@@ -284,43 +284,43 @@
An object of the form:
{
+ "nextPageToken": "A String", # Token to retrieve the next page of results in the list.
"drafts": [ # List of drafts. Note that the `Message` property in each `Draft` resource only contains an `id` and a `threadId`. The messages.get method can fetch additional message details.
{ # A draft email in the user's mailbox.
- "id": "A String", # The immutable ID of the draft.
- "message": { # An email message. # The message content of the draft.
- "internalDate": "A String", # The internal message creation timestamp (epoch ms), which determines ordering in the inbox. For normal SMTP-received email, this represents the time the message was originally accepted by Google, which is more reliable than the `Date` header. However, for API-migrated mail, it can be configured by client to be based on the `Date` header.
- "id": "A String", # The immutable ID of the message.
- "sizeEstimate": 42, # Estimated size in bytes of the message.
- "threadId": "A String", # The ID of the thread the message belongs to. To add a message or draft to a thread, the following criteria must be met: 1. The requested `threadId` must be specified on the `Message` or `Draft.Message` you supply with your request. 2. The `References` and `In-Reply-To` headers must be set in compliance with the [RFC 2822](https://tools.ietf.org/html/rfc2822) standard. 3. The `Subject` headers must match.
- "snippet": "A String", # A short part of the message text.
- "labelIds": [ # List of IDs of labels applied to this message.
- "A String",
- ],
- "historyId": "A String", # The ID of the last history record that modified this message.
- "payload": { # A single MIME message part. # The parsed email structure in the message parts.
- "parts": [ # The child MIME message parts of this part. This only applies to container MIME message parts, for example `multipart/*`. For non- container MIME message part types, such as `text/plain`, this field is empty. For more information, see RFC 1521.
- # Object with schema name: MessagePart
- ],
- "headers": [ # List of headers on this message part. For the top-level message part, representing the entire message payload, it will contain the standard RFC 2822 email headers such as `To`, `From`, and `Subject`.
- {
- "value": "A String", # The value of the header after the `:` separator. For example, `someuser@example.com`.
- "name": "A String", # The name of the header before the `:` separator. For example, `To`.
+ "message": { # An email message. # The message content of the draft.
+ "historyId": "A String", # The ID of the last history record that modified this message.
+ "payload": { # A single MIME message part. # The parsed email structure in the message parts.
+ "parts": [ # The child MIME message parts of this part. This only applies to container MIME message parts, for example `multipart/*`. For non- container MIME message part types, such as `text/plain`, this field is empty. For more information, see RFC 1521.
+ # Object with schema name: MessagePart
+ ],
+ "mimeType": "A String", # The MIME type of the message part.
+ "partId": "A String", # The immutable ID of the message part.
+ "filename": "A String", # The filename of the attachment. Only present if this message part represents an attachment.
+ "headers": [ # List of headers on this message part. For the top-level message part, representing the entire message payload, it will contain the standard RFC 2822 email headers such as `To`, `From`, and `Subject`.
+ {
+ "value": "A String", # The value of the header after the `:` separator. For example, `someuser@example.com`.
+ "name": "A String", # The name of the header before the `:` separator. For example, `To`.
+ },
+ ],
+ "body": { # The body of a single MIME message part. # The message part body for this part, which may be empty for container MIME message parts.
+ "data": "A String", # The body data of a MIME message part as a base64url encoded string. May be empty for MIME container types that have no message body or when the body data is sent as a separate attachment. An attachment ID is present if the body data is contained in a separate attachment.
+ "size": 42, # Number of bytes for the message part data (encoding notwithstanding).
+ "attachmentId": "A String", # When present, contains the ID of an external attachment that can be retrieved in a separate `messages.attachments.get` request. When not present, the entire content of the message part body is contained in the data field.
},
- ],
- "partId": "A String", # The immutable ID of the message part.
- "mimeType": "A String", # The MIME type of the message part.
- "filename": "A String", # The filename of the attachment. Only present if this message part represents an attachment.
- "body": { # The body of a single MIME message part. # The message part body for this part, which may be empty for container MIME message parts.
- "data": "A String", # The body data of a MIME message part as a base64url encoded string. May be empty for MIME container types that have no message body or when the body data is sent as a separate attachment. An attachment ID is present if the body data is contained in a separate attachment.
- "attachmentId": "A String", # When present, contains the ID of an external attachment that can be retrieved in a separate `messages.attachments.get` request. When not present, the entire content of the message part body is contained in the data field.
- "size": 42, # Number of bytes for the message part data (encoding notwithstanding).
},
+ "labelIds": [ # List of IDs of labels applied to this message.
+ "A String",
+ ],
+ "internalDate": "A String", # The internal message creation timestamp (epoch ms), which determines ordering in the inbox. For normal SMTP-received email, this represents the time the message was originally accepted by Google, which is more reliable than the `Date` header. However, for API-migrated mail, it can be configured by client to be based on the `Date` header.
+ "id": "A String", # The immutable ID of the message.
+ "sizeEstimate": 42, # Estimated size in bytes of the message.
+ "raw": "A String", # The entire email message in an RFC 2822 formatted and base64url encoded string. Returned in `messages.get` and `drafts.get` responses when the `format=RAW` parameter is supplied.
+ "snippet": "A String", # A short part of the message text.
+ "threadId": "A String", # The ID of the thread the message belongs to. To add a message or draft to a thread, the following criteria must be met: 1. The requested `threadId` must be specified on the `Message` or `Draft.Message` you supply with your request. 2. The `References` and `In-Reply-To` headers must be set in compliance with the [RFC 2822](https://tools.ietf.org/html/rfc2822) standard. 3. The `Subject` headers must match.
},
- "raw": "A String", # The entire email message in an RFC 2822 formatted and base64url encoded string. Returned in `messages.get` and `drafts.get` responses when the `format=RAW` parameter is supplied.
+ "id": "A String", # The immutable ID of the draft.
},
- },
],
- "nextPageToken": "A String", # Token to retrieve the next page of results in the list.
"resultSizeEstimate": 42, # Estimated total number of results.
}</pre>
</div>
@@ -349,39 +349,39 @@
The object takes the form of:
{ # A draft email in the user's mailbox.
- "id": "A String", # The immutable ID of the draft.
- "message": { # An email message. # The message content of the draft.
- "internalDate": "A String", # The internal message creation timestamp (epoch ms), which determines ordering in the inbox. For normal SMTP-received email, this represents the time the message was originally accepted by Google, which is more reliable than the `Date` header. However, for API-migrated mail, it can be configured by client to be based on the `Date` header.
- "id": "A String", # The immutable ID of the message.
- "sizeEstimate": 42, # Estimated size in bytes of the message.
- "threadId": "A String", # The ID of the thread the message belongs to. To add a message or draft to a thread, the following criteria must be met: 1. The requested `threadId` must be specified on the `Message` or `Draft.Message` you supply with your request. 2. The `References` and `In-Reply-To` headers must be set in compliance with the [RFC 2822](https://tools.ietf.org/html/rfc2822) standard. 3. The `Subject` headers must match.
- "snippet": "A String", # A short part of the message text.
- "labelIds": [ # List of IDs of labels applied to this message.
- "A String",
- ],
- "historyId": "A String", # The ID of the last history record that modified this message.
- "payload": { # A single MIME message part. # The parsed email structure in the message parts.
- "parts": [ # The child MIME message parts of this part. This only applies to container MIME message parts, for example `multipart/*`. For non- container MIME message part types, such as `text/plain`, this field is empty. For more information, see RFC 1521.
- # Object with schema name: MessagePart
- ],
- "headers": [ # List of headers on this message part. For the top-level message part, representing the entire message payload, it will contain the standard RFC 2822 email headers such as `To`, `From`, and `Subject`.
- {
- "value": "A String", # The value of the header after the `:` separator. For example, `someuser@example.com`.
- "name": "A String", # The name of the header before the `:` separator. For example, `To`.
+ "message": { # An email message. # The message content of the draft.
+ "historyId": "A String", # The ID of the last history record that modified this message.
+ "payload": { # A single MIME message part. # The parsed email structure in the message parts.
+ "parts": [ # The child MIME message parts of this part. This only applies to container MIME message parts, for example `multipart/*`. For non- container MIME message part types, such as `text/plain`, this field is empty. For more information, see RFC 1521.
+ # Object with schema name: MessagePart
+ ],
+ "mimeType": "A String", # The MIME type of the message part.
+ "partId": "A String", # The immutable ID of the message part.
+ "filename": "A String", # The filename of the attachment. Only present if this message part represents an attachment.
+ "headers": [ # List of headers on this message part. For the top-level message part, representing the entire message payload, it will contain the standard RFC 2822 email headers such as `To`, `From`, and `Subject`.
+ {
+ "value": "A String", # The value of the header after the `:` separator. For example, `someuser@example.com`.
+ "name": "A String", # The name of the header before the `:` separator. For example, `To`.
+ },
+ ],
+ "body": { # The body of a single MIME message part. # The message part body for this part, which may be empty for container MIME message parts.
+ "data": "A String", # The body data of a MIME message part as a base64url encoded string. May be empty for MIME container types that have no message body or when the body data is sent as a separate attachment. An attachment ID is present if the body data is contained in a separate attachment.
+ "size": 42, # Number of bytes for the message part data (encoding notwithstanding).
+ "attachmentId": "A String", # When present, contains the ID of an external attachment that can be retrieved in a separate `messages.attachments.get` request. When not present, the entire content of the message part body is contained in the data field.
},
- ],
- "partId": "A String", # The immutable ID of the message part.
- "mimeType": "A String", # The MIME type of the message part.
- "filename": "A String", # The filename of the attachment. Only present if this message part represents an attachment.
- "body": { # The body of a single MIME message part. # The message part body for this part, which may be empty for container MIME message parts.
- "data": "A String", # The body data of a MIME message part as a base64url encoded string. May be empty for MIME container types that have no message body or when the body data is sent as a separate attachment. An attachment ID is present if the body data is contained in a separate attachment.
- "attachmentId": "A String", # When present, contains the ID of an external attachment that can be retrieved in a separate `messages.attachments.get` request. When not present, the entire content of the message part body is contained in the data field.
- "size": 42, # Number of bytes for the message part data (encoding notwithstanding).
},
+ "labelIds": [ # List of IDs of labels applied to this message.
+ "A String",
+ ],
+ "internalDate": "A String", # The internal message creation timestamp (epoch ms), which determines ordering in the inbox. For normal SMTP-received email, this represents the time the message was originally accepted by Google, which is more reliable than the `Date` header. However, for API-migrated mail, it can be configured by client to be based on the `Date` header.
+ "id": "A String", # The immutable ID of the message.
+ "sizeEstimate": 42, # Estimated size in bytes of the message.
+ "raw": "A String", # The entire email message in an RFC 2822 formatted and base64url encoded string. Returned in `messages.get` and `drafts.get` responses when the `format=RAW` parameter is supplied.
+ "snippet": "A String", # A short part of the message text.
+ "threadId": "A String", # The ID of the thread the message belongs to. To add a message or draft to a thread, the following criteria must be met: 1. The requested `threadId` must be specified on the `Message` or `Draft.Message` you supply with your request. 2. The `References` and `In-Reply-To` headers must be set in compliance with the [RFC 2822](https://tools.ietf.org/html/rfc2822) standard. 3. The `Subject` headers must match.
},
- "raw": "A String", # The entire email message in an RFC 2822 formatted and base64url encoded string. Returned in `messages.get` and `drafts.get` responses when the `format=RAW` parameter is supplied.
- },
-}
+ "id": "A String", # The immutable ID of the draft.
+ }
x__xgafv: string, V1 error format.
Allowed values
@@ -394,35 +394,35 @@
An object of the form:
{ # An email message.
- "internalDate": "A String", # The internal message creation timestamp (epoch ms), which determines ordering in the inbox. For normal SMTP-received email, this represents the time the message was originally accepted by Google, which is more reliable than the `Date` header. However, for API-migrated mail, it can be configured by client to be based on the `Date` header.
- "id": "A String", # The immutable ID of the message.
- "sizeEstimate": 42, # Estimated size in bytes of the message.
- "threadId": "A String", # The ID of the thread the message belongs to. To add a message or draft to a thread, the following criteria must be met: 1. The requested `threadId` must be specified on the `Message` or `Draft.Message` you supply with your request. 2. The `References` and `In-Reply-To` headers must be set in compliance with the [RFC 2822](https://tools.ietf.org/html/rfc2822) standard. 3. The `Subject` headers must match.
- "snippet": "A String", # A short part of the message text.
- "labelIds": [ # List of IDs of labels applied to this message.
- "A String",
- ],
"historyId": "A String", # The ID of the last history record that modified this message.
"payload": { # A single MIME message part. # The parsed email structure in the message parts.
"parts": [ # The child MIME message parts of this part. This only applies to container MIME message parts, for example `multipart/*`. For non- container MIME message part types, such as `text/plain`, this field is empty. For more information, see RFC 1521.
# Object with schema name: MessagePart
],
+ "mimeType": "A String", # The MIME type of the message part.
+ "partId": "A String", # The immutable ID of the message part.
+ "filename": "A String", # The filename of the attachment. Only present if this message part represents an attachment.
"headers": [ # List of headers on this message part. For the top-level message part, representing the entire message payload, it will contain the standard RFC 2822 email headers such as `To`, `From`, and `Subject`.
{
"value": "A String", # The value of the header after the `:` separator. For example, `someuser@example.com`.
"name": "A String", # The name of the header before the `:` separator. For example, `To`.
},
],
- "partId": "A String", # The immutable ID of the message part.
- "mimeType": "A String", # The MIME type of the message part.
- "filename": "A String", # The filename of the attachment. Only present if this message part represents an attachment.
"body": { # The body of a single MIME message part. # The message part body for this part, which may be empty for container MIME message parts.
"data": "A String", # The body data of a MIME message part as a base64url encoded string. May be empty for MIME container types that have no message body or when the body data is sent as a separate attachment. An attachment ID is present if the body data is contained in a separate attachment.
- "attachmentId": "A String", # When present, contains the ID of an external attachment that can be retrieved in a separate `messages.attachments.get` request. When not present, the entire content of the message part body is contained in the data field.
"size": 42, # Number of bytes for the message part data (encoding notwithstanding).
+ "attachmentId": "A String", # When present, contains the ID of an external attachment that can be retrieved in a separate `messages.attachments.get` request. When not present, the entire content of the message part body is contained in the data field.
},
},
+ "labelIds": [ # List of IDs of labels applied to this message.
+ "A String",
+ ],
+ "internalDate": "A String", # The internal message creation timestamp (epoch ms), which determines ordering in the inbox. For normal SMTP-received email, this represents the time the message was originally accepted by Google, which is more reliable than the `Date` header. However, for API-migrated mail, it can be configured by client to be based on the `Date` header.
+ "id": "A String", # The immutable ID of the message.
+ "sizeEstimate": 42, # Estimated size in bytes of the message.
"raw": "A String", # The entire email message in an RFC 2822 formatted and base64url encoded string. Returned in `messages.get` and `drafts.get` responses when the `format=RAW` parameter is supplied.
+ "snippet": "A String", # A short part of the message text.
+ "threadId": "A String", # The ID of the thread the message belongs to. To add a message or draft to a thread, the following criteria must be met: 1. The requested `threadId` must be specified on the `Message` or `Draft.Message` you supply with your request. 2. The `References` and `In-Reply-To` headers must be set in compliance with the [RFC 2822](https://tools.ietf.org/html/rfc2822) standard. 3. The `Subject` headers must match.
}</pre>
</div>
@@ -437,39 +437,39 @@
The object takes the form of:
{ # A draft email in the user's mailbox.
- "id": "A String", # The immutable ID of the draft.
- "message": { # An email message. # The message content of the draft.
- "internalDate": "A String", # The internal message creation timestamp (epoch ms), which determines ordering in the inbox. For normal SMTP-received email, this represents the time the message was originally accepted by Google, which is more reliable than the `Date` header. However, for API-migrated mail, it can be configured by client to be based on the `Date` header.
- "id": "A String", # The immutable ID of the message.
- "sizeEstimate": 42, # Estimated size in bytes of the message.
- "threadId": "A String", # The ID of the thread the message belongs to. To add a message or draft to a thread, the following criteria must be met: 1. The requested `threadId` must be specified on the `Message` or `Draft.Message` you supply with your request. 2. The `References` and `In-Reply-To` headers must be set in compliance with the [RFC 2822](https://tools.ietf.org/html/rfc2822) standard. 3. The `Subject` headers must match.
- "snippet": "A String", # A short part of the message text.
- "labelIds": [ # List of IDs of labels applied to this message.
- "A String",
- ],
- "historyId": "A String", # The ID of the last history record that modified this message.
- "payload": { # A single MIME message part. # The parsed email structure in the message parts.
- "parts": [ # The child MIME message parts of this part. This only applies to container MIME message parts, for example `multipart/*`. For non- container MIME message part types, such as `text/plain`, this field is empty. For more information, see RFC 1521.
- # Object with schema name: MessagePart
- ],
- "headers": [ # List of headers on this message part. For the top-level message part, representing the entire message payload, it will contain the standard RFC 2822 email headers such as `To`, `From`, and `Subject`.
- {
- "value": "A String", # The value of the header after the `:` separator. For example, `someuser@example.com`.
- "name": "A String", # The name of the header before the `:` separator. For example, `To`.
+ "message": { # An email message. # The message content of the draft.
+ "historyId": "A String", # The ID of the last history record that modified this message.
+ "payload": { # A single MIME message part. # The parsed email structure in the message parts.
+ "parts": [ # The child MIME message parts of this part. This only applies to container MIME message parts, for example `multipart/*`. For non- container MIME message part types, such as `text/plain`, this field is empty. For more information, see RFC 1521.
+ # Object with schema name: MessagePart
+ ],
+ "mimeType": "A String", # The MIME type of the message part.
+ "partId": "A String", # The immutable ID of the message part.
+ "filename": "A String", # The filename of the attachment. Only present if this message part represents an attachment.
+ "headers": [ # List of headers on this message part. For the top-level message part, representing the entire message payload, it will contain the standard RFC 2822 email headers such as `To`, `From`, and `Subject`.
+ {
+ "value": "A String", # The value of the header after the `:` separator. For example, `someuser@example.com`.
+ "name": "A String", # The name of the header before the `:` separator. For example, `To`.
+ },
+ ],
+ "body": { # The body of a single MIME message part. # The message part body for this part, which may be empty for container MIME message parts.
+ "data": "A String", # The body data of a MIME message part as a base64url encoded string. May be empty for MIME container types that have no message body or when the body data is sent as a separate attachment. An attachment ID is present if the body data is contained in a separate attachment.
+ "size": 42, # Number of bytes for the message part data (encoding notwithstanding).
+ "attachmentId": "A String", # When present, contains the ID of an external attachment that can be retrieved in a separate `messages.attachments.get` request. When not present, the entire content of the message part body is contained in the data field.
},
- ],
- "partId": "A String", # The immutable ID of the message part.
- "mimeType": "A String", # The MIME type of the message part.
- "filename": "A String", # The filename of the attachment. Only present if this message part represents an attachment.
- "body": { # The body of a single MIME message part. # The message part body for this part, which may be empty for container MIME message parts.
- "data": "A String", # The body data of a MIME message part as a base64url encoded string. May be empty for MIME container types that have no message body or when the body data is sent as a separate attachment. An attachment ID is present if the body data is contained in a separate attachment.
- "attachmentId": "A String", # When present, contains the ID of an external attachment that can be retrieved in a separate `messages.attachments.get` request. When not present, the entire content of the message part body is contained in the data field.
- "size": 42, # Number of bytes for the message part data (encoding notwithstanding).
},
+ "labelIds": [ # List of IDs of labels applied to this message.
+ "A String",
+ ],
+ "internalDate": "A String", # The internal message creation timestamp (epoch ms), which determines ordering in the inbox. For normal SMTP-received email, this represents the time the message was originally accepted by Google, which is more reliable than the `Date` header. However, for API-migrated mail, it can be configured by client to be based on the `Date` header.
+ "id": "A String", # The immutable ID of the message.
+ "sizeEstimate": 42, # Estimated size in bytes of the message.
+ "raw": "A String", # The entire email message in an RFC 2822 formatted and base64url encoded string. Returned in `messages.get` and `drafts.get` responses when the `format=RAW` parameter is supplied.
+ "snippet": "A String", # A short part of the message text.
+ "threadId": "A String", # The ID of the thread the message belongs to. To add a message or draft to a thread, the following criteria must be met: 1. The requested `threadId` must be specified on the `Message` or `Draft.Message` you supply with your request. 2. The `References` and `In-Reply-To` headers must be set in compliance with the [RFC 2822](https://tools.ietf.org/html/rfc2822) standard. 3. The `Subject` headers must match.
},
- "raw": "A String", # The entire email message in an RFC 2822 formatted and base64url encoded string. Returned in `messages.get` and `drafts.get` responses when the `format=RAW` parameter is supplied.
- },
-}
+ "id": "A String", # The immutable ID of the draft.
+ }
x__xgafv: string, V1 error format.
Allowed values
@@ -482,39 +482,39 @@
An object of the form:
{ # A draft email in the user's mailbox.
- "id": "A String", # The immutable ID of the draft.
- "message": { # An email message. # The message content of the draft.
- "internalDate": "A String", # The internal message creation timestamp (epoch ms), which determines ordering in the inbox. For normal SMTP-received email, this represents the time the message was originally accepted by Google, which is more reliable than the `Date` header. However, for API-migrated mail, it can be configured by client to be based on the `Date` header.
- "id": "A String", # The immutable ID of the message.
- "sizeEstimate": 42, # Estimated size in bytes of the message.
- "threadId": "A String", # The ID of the thread the message belongs to. To add a message or draft to a thread, the following criteria must be met: 1. The requested `threadId` must be specified on the `Message` or `Draft.Message` you supply with your request. 2. The `References` and `In-Reply-To` headers must be set in compliance with the [RFC 2822](https://tools.ietf.org/html/rfc2822) standard. 3. The `Subject` headers must match.
- "snippet": "A String", # A short part of the message text.
- "labelIds": [ # List of IDs of labels applied to this message.
- "A String",
- ],
- "historyId": "A String", # The ID of the last history record that modified this message.
- "payload": { # A single MIME message part. # The parsed email structure in the message parts.
- "parts": [ # The child MIME message parts of this part. This only applies to container MIME message parts, for example `multipart/*`. For non- container MIME message part types, such as `text/plain`, this field is empty. For more information, see RFC 1521.
- # Object with schema name: MessagePart
- ],
- "headers": [ # List of headers on this message part. For the top-level message part, representing the entire message payload, it will contain the standard RFC 2822 email headers such as `To`, `From`, and `Subject`.
- {
- "value": "A String", # The value of the header after the `:` separator. For example, `someuser@example.com`.
- "name": "A String", # The name of the header before the `:` separator. For example, `To`.
+ "message": { # An email message. # The message content of the draft.
+ "historyId": "A String", # The ID of the last history record that modified this message.
+ "payload": { # A single MIME message part. # The parsed email structure in the message parts.
+ "parts": [ # The child MIME message parts of this part. This only applies to container MIME message parts, for example `multipart/*`. For non- container MIME message part types, such as `text/plain`, this field is empty. For more information, see RFC 1521.
+ # Object with schema name: MessagePart
+ ],
+ "mimeType": "A String", # The MIME type of the message part.
+ "partId": "A String", # The immutable ID of the message part.
+ "filename": "A String", # The filename of the attachment. Only present if this message part represents an attachment.
+ "headers": [ # List of headers on this message part. For the top-level message part, representing the entire message payload, it will contain the standard RFC 2822 email headers such as `To`, `From`, and `Subject`.
+ {
+ "value": "A String", # The value of the header after the `:` separator. For example, `someuser@example.com`.
+ "name": "A String", # The name of the header before the `:` separator. For example, `To`.
+ },
+ ],
+ "body": { # The body of a single MIME message part. # The message part body for this part, which may be empty for container MIME message parts.
+ "data": "A String", # The body data of a MIME message part as a base64url encoded string. May be empty for MIME container types that have no message body or when the body data is sent as a separate attachment. An attachment ID is present if the body data is contained in a separate attachment.
+ "size": 42, # Number of bytes for the message part data (encoding notwithstanding).
+ "attachmentId": "A String", # When present, contains the ID of an external attachment that can be retrieved in a separate `messages.attachments.get` request. When not present, the entire content of the message part body is contained in the data field.
},
- ],
- "partId": "A String", # The immutable ID of the message part.
- "mimeType": "A String", # The MIME type of the message part.
- "filename": "A String", # The filename of the attachment. Only present if this message part represents an attachment.
- "body": { # The body of a single MIME message part. # The message part body for this part, which may be empty for container MIME message parts.
- "data": "A String", # The body data of a MIME message part as a base64url encoded string. May be empty for MIME container types that have no message body or when the body data is sent as a separate attachment. An attachment ID is present if the body data is contained in a separate attachment.
- "attachmentId": "A String", # When present, contains the ID of an external attachment that can be retrieved in a separate `messages.attachments.get` request. When not present, the entire content of the message part body is contained in the data field.
- "size": 42, # Number of bytes for the message part data (encoding notwithstanding).
},
+ "labelIds": [ # List of IDs of labels applied to this message.
+ "A String",
+ ],
+ "internalDate": "A String", # The internal message creation timestamp (epoch ms), which determines ordering in the inbox. For normal SMTP-received email, this represents the time the message was originally accepted by Google, which is more reliable than the `Date` header. However, for API-migrated mail, it can be configured by client to be based on the `Date` header.
+ "id": "A String", # The immutable ID of the message.
+ "sizeEstimate": 42, # Estimated size in bytes of the message.
+ "raw": "A String", # The entire email message in an RFC 2822 formatted and base64url encoded string. Returned in `messages.get` and `drafts.get` responses when the `format=RAW` parameter is supplied.
+ "snippet": "A String", # A short part of the message text.
+ "threadId": "A String", # The ID of the thread the message belongs to. To add a message or draft to a thread, the following criteria must be met: 1. The requested `threadId` must be specified on the `Message` or `Draft.Message` you supply with your request. 2. The `References` and `In-Reply-To` headers must be set in compliance with the [RFC 2822](https://tools.ietf.org/html/rfc2822) standard. 3. The `Subject` headers must match.
},
- "raw": "A String", # The entire email message in an RFC 2822 formatted and base64url encoded string. Returned in `messages.get` and `drafts.get` responses when the `format=RAW` parameter is supplied.
- },
- }</pre>
+ "id": "A String", # The immutable ID of the draft.
+ }</pre>
</div>
</body></html>
\ No newline at end of file