---
title: "POST /v2/activity:query"
method: POST
path: "/v2/activity:query"
tags: ["activity"]
---

# POST /v2/activity:query

`POST /v2/activity:query`

Query past activity in Google Drive.

## Request body

- QueryDriveActivityRequest — The request message for querying Drive activity.
  - `itemName` string — Return activities for this Drive item. The format is `items/ITEM_ID`.
  - `ancestorName` string — Return activities for this Drive folder, plus all children and descendants. The format is `items/ITEM_ID`.
  - `pageSize` integer — The minimum number of activities desired in the response; the server attempts to return at least this quantity. The server may also return fewer activities if it has a partial response ready before the request times out. If not set, a default value is used.
  - `pageToken` string — The token identifies which page of results to return. Set this to the next_page_token value returned from a previous query to obtain the following page of results. If not set, the first page of results is returned.
  - `filter` string — The filtering for items returned from this query request. The format of the filter string is a sequence of expressions, joined by an optional "AND", where each expression is of the form "field operator value". Supported fields: - `time`: Uses numerical operators on date values either in terms of milliseconds since Jan 1, 1970 or in RFC 3339 format. Examples: - `time > 1452409200000 AND time <= 1492812924310` - `time >= "2016-01-10T01:02:03-05:00"` - `detail.action_detail_case`: Uses the "has" operator (:) and either a singular value or a list of allowed action types enclosed in parentheses, separated by a space. To exclude a result from the response, prepend a hyphen (`-`) to the beginning of the filter string. Examples: - `detail.action_detail_case:RENAME` - `detail.action_detail_case:(CREATE RESTORE)` - `-detail.action_detail_case:MOVE`
  - `consolidationStrategy` ConsolidationStrategy — How the individual activities are consolidated. If a set of activities is related they can be consolidated into one combined activity, such as one actor performing the same action on multiple targets, or multiple actors performing the same action on a single target. The strategy defines the rules for which activities are related.
    - `legacy` Legacy — A strategy that consolidates activities using the grouping rules from the legacy V1 Activity API. Similar actions occurring within a window of time can be grouped across multiple targets (such as moving a set of files at once) or multiple actors (such as several users editing the same item). Grouping rules for this strategy are specific to each type of action.
    - `none` NoConsolidation — A strategy that does no consolidation of individual activities.

## Response `200`

Successful response

---

[API](https://skmtc.dev/google/apis/driveactivity.md) · [All operations](https://skmtc.dev/google/apis/driveactivity/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/google/driveactivity/revisions/3be0ffadd929/schema)