Hi there! Are you looking for the official Deno documentation? Try docs.deno.com for all your Deno learning needs.

UsersHistoryListOptions

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

Additional options for Gmail#usersHistoryList.

interface UsersHistoryListOptions {
historyTypes?:
| "messageAdded"
| "messageDeleted"
| "labelAdded"
| "labelRemoved";
labelId?: string;
maxResults?: number;
pageToken?: string;
startHistoryId?: bigint;
}

§Properties

§
historyTypes?: "messageAdded" | "messageDeleted" | "labelAdded" | "labelRemoved"
[src]

History types to be returned by the function

§
labelId?: string
[src]

Only return messages with a label matching the ID.

§
maxResults?: number
[src]

Maximum number of history records to return. This field defaults to 100. The maximum allowed value for this field is 500.

§
pageToken?: string
[src]

Page token to retrieve a specific page of results in the list.

§
startHistoryId?: bigint
[src]

Required. Returns history records after the specified startHistoryId. The supplied startHistoryId should be obtained from the historyId of a message, thread, or previous list response. History IDs increase chronologically but are not contiguous with random gaps in between valid IDs. Supplying an invalid or out of date startHistoryId typically returns an HTTP 404 error code. A historyId is typically valid for at least a week, but in some rare circumstances may be valid for only a few hours. If you receive an HTTP 404 error response, your application should perform a full sync. If you receive no nextPageToken in the response, there are no updates to retrieve and you can store the returned historyId for a future request.