Message

import type { Message } from "https://googleapis.deno.dev/v1/gmail:v1.ts";

An email message.

interface Message {

classificationLabelValues?: ClassificationLabelValue[];

historyId?: bigint;

id?: string;

internalDate?: bigint;

labelIds?: string[];

payload?: MessagePart;

raw?: Uint8Array;

sizeEstimate?: number;

snippet?: string;

threadId?: string;

}

§Properties

classificationLabelValues?: ClassificationLabelValue[]

[src]

Classification Label values on the message. Available Classification Label schemas can be queried using the Google Drive Labels API. Each classification label ID must be unique. If duplicate IDs are provided, only one will be retained, and the selection is arbitrary. Only used for Google Workspace accounts.

historyId?: bigint

[src]

The ID of the last history record that modified this message.

id?: string

[src]

The immutable ID of the message.

internalDate?: bigint

[src]

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.

labelIds?: string[]

[src]

List of IDs of labels applied to this message.

payload?: MessagePart

[src]

The parsed email structure in the message parts.

raw?: Uint8Array

[src]

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.

sizeEstimate?: number

[src]

Estimated size in bytes of the message.

snippet?: string

[src]

A short part of the message text.

threadId?: string

[src]

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 standard. 3. The Subject headers must match.