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
GET https://{TRANSLATION_GDC_ENDPOINT}/v3/{name}/operations
Path parameters
Parameters
name
string
The name of the operation's parent resource.
Query parameters
Parameters
filter
string
The standard list filter.
page_size
integer
The standard list page size.
page_token
string
The standard list page token.
Request body
The request body must be empty.
Response body
If successful, the response body contains data with the following structure:
The response message for Operations.ListOperations.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-07-10 UTC."],[[["\u003cp\u003eThis endpoint lists operations that match a specified filter, returning \u003ccode\u003eUNIMPLEMENTED\u003c/code\u003e if the server does not support this method.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003ename\u003c/code\u003e parameter in the path specifies the parent resource for operations, with a default format that includes the operations collection ID, which can be overridden using specific bindings.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003efilter\u003c/code\u003e query parameter enables filtering the list of operations, and pagination can be managed through the \u003ccode\u003epage_size\u003c/code\u003e and \u003ccode\u003epage_token\u003c/code\u003e query parameters.\u003c/p\u003e\n"],["\u003cp\u003eThe response body contains an array of operation objects, in addition to the \u003ccode\u003enext_page_token\u003c/code\u003e used for pagination.\u003c/p\u003e\n"]]],[],null,["# Method: projects.operations.list\n\nLists operations that match the specified filter in the request. If the server doesn't support this method, it returns `UNIMPLEMENTED`.\n\nNOTE: 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.\n\n### HTTP request\n\n`GET https://{TRANSLATION_GDC_ENDPOINT}/v3/{name}/operations`\n\n### Path parameters\n\n### Query parameters\n\n### Request body\n\nThe request body must be empty.\n\n### Response body\n\nIf successful, the response body contains data with the following structure:\nThe response message for `Operations.ListOperations`."]]
