Method: operations.list

Stay organized with collections Save and categorize content based on your preferences.

Lists operations that match the specified filter in the request. If the server doesn't support this method, it returns UNIMPLEMENTED.

NOTE: the name binding allows API services to override the binding to use different resource name schemes, such as users/*/operations. To override the binding, API services can add a binding such as "/v1/{name=users/*}/operations" to their service configuration. For backwards compatibility, the default name includes the operations collection id, however overriding users must ensure the name binding is the parent resource, without the operations collection id.

HTTP request


Query parameters



Must not be set.



Required. A filter for matching the requested operations.

The supported formats of filter are:
To query for a specific function:


To query for all of the latest operations for a project:




The maximum number of records that should be returned.
Requested page size cannot exceed 100. If not set, the default page size is 100.

Pagination is only supported when querying for a specific function.



Token identifying which result to start with, which is returned by a previous list call.

Pagination is only supported when querying for a specific function.

Request body

The request body must be empty.

Response body

If successful, the response body contains an instance of ListOperationsResponse.

Authorization Scopes

Requires one of the following OAuth scopes:


For more information, see the Authentication Overview.