docs: update docs/dyn (#1096)
This PR was generated using Autosynth. :rainbow:
Synth log will be available here:
https://source.cloud.google.com/results/invocations/6f0f288a-a1e8-4b2d-a85f-00b1c6150185/targets
- [ ] To automatically regenerate this PR, check this box.
Source-Link: https://github.com/googleapis/synthtool/commit/39b7149da4026765385403632db3c6f63db96b2c
Source-Link: https://github.com/googleapis/synthtool/commit/9a7d9fbb7045c34c9d3d22c1ff766eeae51f04c9
Source-Link: https://github.com/googleapis/synthtool/commit/dc9903a8c30c3662b6098f0e4a97f221d67268b2
Source-Link: https://github.com/googleapis/synthtool/commit/7fcc405a579d5d53a726ff3da1b7c8c08f0f2d58
Source-Link: https://github.com/googleapis/synthtool/commit/d5fc0bcf9ea9789c5b0e3154a9e3b29e5cea6116
Source-Link: https://github.com/googleapis/synthtool/commit/e89175cf074dccc4babb4eca66ae913696e47a71
Source-Link: https://github.com/googleapis/synthtool/commit/7d652819519dfa24da9e14548232e4aaba71a11c
Source-Link: https://github.com/googleapis/synthtool/commit/7db8a6c5ffb12a6e4c2f799c18f00f7f3d60e279
Source-Link: https://github.com/googleapis/synthtool/commit/1f1148d3c7a7a52f0c98077f976bd9b3c948ee2b
Source-Link: https://github.com/googleapis/synthtool/commit/2c8aecedd55b0480fb4e123b6e07fa5b12953862
Source-Link: https://github.com/googleapis/synthtool/commit/3d3e94c4e02370f307a9a200b0c743c3d8d19f29
Source-Link: https://github.com/googleapis/synthtool/commit/c7824ea48ff6d4d42dfae0849aec8a85acd90bd9
Source-Link: https://github.com/googleapis/synthtool/commit/ba9918cd22874245b55734f57470c719b577e591
Source-Link: https://github.com/googleapis/synthtool/commit/b19b401571e77192f8dd38eab5fb2300a0de9324
Source-Link: https://github.com/googleapis/synthtool/commit/6542bd723403513626f61642fc02ddca528409aa
diff --git a/docs/dyn/gmail_v1.users.threads.html b/docs/dyn/gmail_v1.users.threads.html
index 20d2af0..53096e9 100644
--- a/docs/dyn/gmail_v1.users.threads.html
+++ b/docs/dyn/gmail_v1.users.threads.html
@@ -81,10 +81,10 @@
<code><a href="#delete">delete(userId, id, x__xgafv=None)</a></code></p>
<p class="firstline">Immediately and permanently deletes the specified thread. This operation cannot be undone. Prefer `threads.trash` instead.</p>
<p class="toc_element">
- <code><a href="#get">get(userId, id, metadataHeaders=None, format=None, x__xgafv=None)</a></code></p>
+ <code><a href="#get">get(userId, id, format=None, metadataHeaders=None, x__xgafv=None)</a></code></p>
<p class="firstline">Gets the specified thread.</p>
<p class="toc_element">
- <code><a href="#list">list(userId, pageToken=None, maxResults=None, labelIds=None, includeSpamTrash=None, q=None, x__xgafv=None)</a></code></p>
+ <code><a href="#list">list(userId, labelIds=None, maxResults=None, includeSpamTrash=None, q=None, pageToken=None, x__xgafv=None)</a></code></p>
<p class="firstline">Lists the threads in the user's mailbox.</p>
<p class="toc_element">
<code><a href="#list_next">list_next(previous_request, previous_response)</a></code></p>
@@ -119,18 +119,18 @@
</div>
<div class="method">
- <code class="details" id="get">get(userId, id, metadataHeaders=None, format=None, x__xgafv=None)</code>
+ <code class="details" id="get">get(userId, id, format=None, metadataHeaders=None, x__xgafv=None)</code>
<pre>Gets the specified thread.
Args:
userId: string, The user's email address. The special value `me` can be used to indicate the authenticated user. (required)
id: string, The ID of the thread to retrieve. (required)
- metadataHeaders: string, When given and format is METADATA, only include headers specified. (repeated)
format: string, The format to return the messages in.
Allowed values
full - Returns the full email message data with body content parsed in the `payload` field; the `raw` field is not used. Format cannot be used when accessing the api using the gmail.metadata scope.
metadata - Returns only email message IDs, labels, and email headers.
minimal - Returns only email message IDs and labels; does not return the email headers, body, or payload.
+ metadataHeaders: string, When given and format is METADATA, only include headers specified. (repeated)
x__xgafv: string, V1 error format.
Allowed values
1 - v1 error format
@@ -140,56 +140,56 @@
An object of the form:
{ # A collection of messages representing a conversation.
+ "id": "A String", # The unique ID of the thread.
"snippet": "A String", # A short part of the message text.
- "historyId": "A String", # The ID of the last history record that modified this thread.
"messages": [ # The list of messages in the thread.
{ # 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.
- "mimeType": "A String", # The MIME type of the message part.
"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`.
{
- "name": "A String", # The name of the header before the `:` separator. For example, `To`.
"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).
- "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.
},
- "partId": "A String", # The immutable ID of the message part.
},
- "id": "A String", # The immutable ID of the 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.
"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.
- "historyId": "A String", # The ID of the last history record that modified this 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.
},
],
- "id": "A String", # The unique ID of the thread.
+ "historyId": "A String", # The ID of the last history record that modified this thread.
}</pre>
</div>
<div class="method">
- <code class="details" id="list">list(userId, pageToken=None, maxResults=None, labelIds=None, includeSpamTrash=None, q=None, x__xgafv=None)</code>
+ <code class="details" id="list">list(userId, labelIds=None, maxResults=None, includeSpamTrash=None, q=None, pageToken=None, x__xgafv=None)</code>
<pre>Lists the threads 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)
- pageToken: string, Page token to retrieve a specific page of results in the list.
- maxResults: integer, Maximum number of threads to return.
labelIds: string, Only return threads with labels that match all of the specified label IDs. (repeated)
+ maxResults: integer, Maximum number of threads to return.
includeSpamTrash: boolean, Include threads from `SPAM` and `TRASH` in the results.
q: string, Only return threads matching the specified query. Supports the same query format as the Gmail search box. For example, `"from:someuser@example.com rfc822msgid: is:unread"`. Parameter cannot be used when accessing the api using the gmail.metadata scope.
+ pageToken: string, Page token to retrieve a specific page of results in the list.
x__xgafv: string, V1 error format.
Allowed values
1 - v1 error format
@@ -199,48 +199,48 @@
An object of the form:
{
+ "nextPageToken": "A String", # Page token to retrieve the next page of results in the list.
+ "resultSizeEstimate": 42, # Estimated total number of results.
"threads": [ # List of threads. Note that each thread resource does not contain a list of `messages`. The list of `messages` for a given thread can be fetched using the threads.get method.
{ # A collection of messages representing a conversation.
+ "id": "A String", # The unique ID of the thread.
"snippet": "A String", # A short part of the message text.
- "historyId": "A String", # The ID of the last history record that modified this thread.
"messages": [ # The list of messages in the thread.
{ # 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.
- "mimeType": "A String", # The MIME type of the message part.
"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`.
{
- "name": "A String", # The name of the header before the `:` separator. For example, `To`.
"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).
- "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.
},
- "partId": "A String", # The immutable ID of the message part.
},
- "id": "A String", # The immutable ID of the 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.
"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.
- "historyId": "A String", # The ID of the last history record that modified this 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.
},
],
- "id": "A String", # The unique ID of the thread.
+ "historyId": "A String", # The ID of the last history record that modified this thread.
},
],
- "resultSizeEstimate": 42, # Estimated total number of results.
- "nextPageToken": "A String", # Page token to retrieve the next page of results in the list.
}</pre>
</div>
@@ -269,10 +269,10 @@
The object takes the form of:
{
- "removeLabelIds": [ # A list of IDs of labels to remove from this thread.
+ "addLabelIds": [ # A list of IDs of labels to add to this thread.
"A String",
],
- "addLabelIds": [ # A list of IDs of labels to add to this thread.
+ "removeLabelIds": [ # A list of IDs of labels to remove from this thread.
"A String",
],
}
@@ -286,42 +286,42 @@
An object of the form:
{ # A collection of messages representing a conversation.
+ "id": "A String", # The unique ID of the thread.
"snippet": "A String", # A short part of the message text.
- "historyId": "A String", # The ID of the last history record that modified this thread.
"messages": [ # The list of messages in the thread.
{ # 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.
- "mimeType": "A String", # The MIME type of the message part.
"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`.
{
- "name": "A String", # The name of the header before the `:` separator. For example, `To`.
"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).
- "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.
},
- "partId": "A String", # The immutable ID of the message part.
},
- "id": "A String", # The immutable ID of the 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.
"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.
- "historyId": "A String", # The ID of the last history record that modified this 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.
},
],
- "id": "A String", # The unique ID of the thread.
+ "historyId": "A String", # The ID of the last history record that modified this thread.
}</pre>
</div>
@@ -341,42 +341,42 @@
An object of the form:
{ # A collection of messages representing a conversation.
+ "id": "A String", # The unique ID of the thread.
"snippet": "A String", # A short part of the message text.
- "historyId": "A String", # The ID of the last history record that modified this thread.
"messages": [ # The list of messages in the thread.
{ # 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.
- "mimeType": "A String", # The MIME type of the message part.
"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`.
{
- "name": "A String", # The name of the header before the `:` separator. For example, `To`.
"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).
- "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.
},
- "partId": "A String", # The immutable ID of the message part.
},
- "id": "A String", # The immutable ID of the 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.
"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.
- "historyId": "A String", # The ID of the last history record that modified this 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.
},
],
- "id": "A String", # The unique ID of the thread.
+ "historyId": "A String", # The ID of the last history record that modified this thread.
}</pre>
</div>
@@ -396,42 +396,42 @@
An object of the form:
{ # A collection of messages representing a conversation.
+ "id": "A String", # The unique ID of the thread.
"snippet": "A String", # A short part of the message text.
- "historyId": "A String", # The ID of the last history record that modified this thread.
"messages": [ # The list of messages in the thread.
{ # 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.
- "mimeType": "A String", # The MIME type of the message part.
"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`.
{
- "name": "A String", # The name of the header before the `:` separator. For example, `To`.
"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).
- "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.
},
- "partId": "A String", # The immutable ID of the message part.
},
- "id": "A String", # The immutable ID of the 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.
"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.
- "historyId": "A String", # The ID of the last history record that modified this 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.
},
],
- "id": "A String", # The unique ID of the thread.
+ "historyId": "A String", # The ID of the last history record that modified this thread.
}</pre>
</div>