Vertex AI Search for Retail API (retail:v2alpha)

2022-02-10

2 new methods

Additions

    Methods
  • retail.projects.operations.get

      Flat Path : v2alpha/projects/{projectsId}/operations/{operationsId}

      Parameters :

        name

          Description : The name of the operation resource.

          Pattern : ^projects/[^/]+/operations/[^/]+$

          Location : path

          Type : string

          Required : Yes

      Path : v2alpha/{+name}

      Parameter Order : name

      HTTP Method : GET

      Scopes : https://www.googleapis.com/auth/cloud-platform

      Description : Gets the latest state of a long-running operation. Clients can use this method to poll the operation result at intervals as recommended by the API service.

  • retail.projects.operations.list

      Parameters :

        pageToken

          Type : string

          Description : The standard list page token.

          Location : query

        name

          Required : Yes

          Type : string

          Location : path

          Description : The name of the operation's parent resource.

          Pattern : ^projects/[^/]+$

        pageSize

          Description : The standard list page size.

          Location : query

          Format : int32

          Type : integer

        filter

          Location : query

          Type : string

          Description : The standard list filter.

      Path : v2alpha/{+name}/operations

      HTTP Method : GET

      Flat Path : v2alpha/projects/{projectsId}/operations

      Parameter Order : name

      Scopes : https://www.googleapis.com/auth/cloud-platform

      Description : 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.