Lists the history of all changes to the given mailbox. History results are returned in chronological order (increasing historyId).
Path parameters
The user's email address. The special value me can be used to indicate the authenticated user
Query parameters
V1 error format
V1 error format
OAuth access token
Data format for response
Data format for response
JSONP
Selector specifying which fields to include in a partial response
API key. Your API key identifies your project and provides you with API access, quota, and reports. Required unless you provide an OAuth 2.0 token
OAuth 2.0 token for the current user
Returns response with indentations and line breaks
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
Upload protocol for media (e.g. "raw", "multipart")
Legacy upload protocol for media (e.g. "media", "multipart")
History types to be returned by the function
Only return messages with a label matching the ID
Maximum number of history records to return. This field defaults to 100. The maximum allowed value for this field is 500
Page token to retrieve a specific page of results in the list
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
Response
Successful response