Method: projects.locations.metadataStores.executions.list

Lists Executions in the MetadataStore.

HTTP request

GET https://{service-endpoint}/v1/{parent}/executions

Where {service-endpoint} is one of the supported service endpoints.

Path parameters



Required. The MetadataStore whose Executions should be listed. Format: projects/{project}/locations/{location}/metadataStores/{metadatastore}

Query parameters



The maximum number of Executions to return. The service may return fewer. Must be in range 1-1000, inclusive. Defaults to 100.



A page token, received from a previous MetadataService.ListExecutions call. Provide this to retrieve the subsequent page.

When paginating, all other provided parameters must match the call that provided the page token. (Otherwise the request will fail with an INVALID_ARGUMENT error.)



Filter specifying the boolean condition for the Executions to satisfy in order to be part of the result set. The syntax to define filter query is based on Following are the supported set of filters:

  • attribute filtering: For example: displayName = "test". Supported fields include: name, displayName, state, schemaTitle, createTime, and updateTime. time fields, such as createTime and updateTime, require values specified in RFC-3339 format. For example: createTime = "2020-11-19T11:30:00-04:00".
  • metadata field: To filter on metadata fields use traversal operation as follows: metadata.<fieldName>.<typeValue> For example: metadata.field_1.number_value = 10.0 In case the field name contains special characters (such as colon), one can embed it inside double quote. For example: metadata."field:1".number_value = 10.0
  • Context based filtering: To filter Executions based on the contexts to which they belong use the function operator with the full resource name: in_context(<context-name>). For example: in_context("projects/<projectNumber>/locations/<location>/metadataStores/<metadatastore_name>/contexts/<context-id>")

Each of the above supported filters can be combined together using logical operators (AND & OR). Maximum nested expression depth allowed is 5.

For example: displayName = "test" AND metadata.field1.bool_value = true.



How the list of messages is ordered. Specify the values to order by and an ordering operation. The default sorting order is ascending. To specify descending order for a field, users append a " desc" suffix; for example: "foo desc, bar". Subfields are specified with a . character, such as see for more details.

Request body

The request body must be empty.

Response body

Response message for MetadataService.ListExecutions.

If successful, the response body contains data with the following structure:

JSON representation
  "executions": [
      object (Execution)
  "nextPageToken": string

object (Execution)

The Executions retrieved from the MetadataStore.



A token, which can be sent as ListExecutionsRequest.page_token to retrieve the next page. If this field is not populated, there are no subsequent pages.

Authorization scopes

Requires the following OAuth scope:


For more information, see the Authentication Overview.

IAM Permissions

Requires the following IAM permission on the parent resource:

  • aiplatform.executions.list

For more information, see the IAM documentation.