Google: Lists the history of all changes to the given mailbox History results are returned in chronological order (increasing `history Id`) For more information, see Synchronize clients with Gmail (https: developers google com workspace gmail api guides sync)
Google gmailUsersHistory.gmailUsersHistoryList: arguments, response, policy and SDK examples.
← gmail_users_history operations · Get started · OpenAPI downloads
Contract 2026-10-27 · Operation google.gmail_users_history_list
Provider route: GET /gmail/v1/users/{userId}/history. Alter supplies the connection’s credentials and routing.
Call through Alter
Section titled “Call through Alter”Install @alter-ai/sdk @alter-ai/google with npm, or alter-sdk-google with pip. Supply your connected customer’s grant ID and the arguments described below.
import { App } from "@alter-ai/sdk";import { GoogleIntegration } from "@alter-ai/google";
async function execute(input: Parameters<GoogleIntegration["gmailUsersHistory"]["gmailUsersHistoryList"]>[0]) { const app = new App({ apiKey: process.env.ALTER_API_KEY! }); try { const provider = new GoogleIntegration(app, { grantId: process.env.PROVIDER_GRANT_ID! }); const call = await provider.gmailUsersHistory.gmailUsersHistoryList(input); const result = await call.wait(); return result.bodyJson(); } finally { await app.close(); }}import osfrom alter_sdk import Appfrom alter_sdk_google import GoogleIntegration
async def execute(arguments): async with App(api_key=os.environ["ALTER_API_KEY"]) as app: provider = GoogleIntegration(app, {"grant_id": os.environ["PROVIDER_GRANT_ID"]}) call = await provider.gmail_users_history.gmail_users_history_list(arguments) result = await call.wait() return result.body_json()| Field | Type | Presence | Description and constraints |
|---|---|---|---|
$ | object | Root | Additional keys: not allowed |
path | object | Required within parent | Additional keys: not allowed |
path.userId | string | Required within parent | The user’s email address. The special value `me` can be used to indicate the authenticated user. Default: me |
query | object | Required within parent | Additional keys: not allowed |
query.fields | string | Optional | Selector specifying which fields to include in a partial response. |
query.prettyPrint | boolean | Optional | Returns response with indentations and line breaks. Default: true |
query.quotaUser | string | Optional | Available to use for quota purposes for server-side applications. Can be any arbitrary string assigned to a user, but should not exceed 40 characters. |
query.historyTypes | array | Optional | |
query.historyTypes[] | string | Each item | History types to be returned by the function One of: messageAdded, messageDeleted, labelAdded, labelRemoved |
query.labelId | string | Optional | Only return messages with a label matching the ID. |
query.maxResults | integer | Optional | Maximum number of history records to return. This field defaults to 100. The maximum allowed value for this field is 500. Default: 100 Format: uint32 |
query.pageToken | string | Optional | Page token to retrieve a specific page of results in the list. |
query.startHistoryId | string | Required within parent | 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. Format: uint64 |
Response
Section titled “Response”Response media type: application/json. The table describes the pinned successful response. Referenced models link to their complete fields.
Policy, approvals and errors
Section titled “Policy, approvals and errors”SDK function policy ID: google.gmail_users_history_list. Catalog operation: gmail.users.history.list. Rules can name either ID; function rules distinguish managed calls and conservatively cover raw calls sharing the route. Existing grant permissions and policy rules apply. wait() returns an immediate result or waits for a required approval; it never approves the request itself. Persist the approval ID to resume after a restart.
Provider errors retain their response; JSON decoding raises ProviderAPIError for provider failures. ManagedOperationError identifies contract/input/retention errors. See error handling and provider-specific behavior. Sensitive input may be refused before approval storage. A decoding error never resubmits a write.
Required provider scopes: ["https://mail.google.com/", "https://www.googleapis.com/auth/gmail.metadata", "https://www.googleapis.com/auth/gmail.modify", "https://www.googleapis.com/auth/gmail.readonly"]