Method: projects.locations.models.mergeVersionAliases

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

Merges a set of aliases for a Model version.

HTTP request

POST https://{service-endpoint}/v1beta1/{name}:mergeVersionAliases

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

Path parameters



Required. The name of the model version to merge aliases, with a version ID explicitly included.

Example: projects/{project}/locations/{location}/models/{model}@1234

Request body

The request body contains data with the following structure:

JSON representation
  "versionAliases": [


Required. The set of version aliases to merge. The alias should be at most 128 characters, and match [a-z][a-zA-Z0-9-]{0,126}[a-z-0-9]. Add the - prefix to an alias means removing that alias from the version. - is NOT counted in the 128 characters. Example: -golden means removing the golden alias from the version.

There is NO ordering in aliases, which means 1) The aliases returned from models.get API might not have the exactly same order from this models.mergeVersionAliases API. 2) Adding and deleting the same alias in the request is not recommended, and the 2 operations will be cancelled out.

Response body

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

Authorization Scopes

Requires the following OAuth scope:


For more information, see the Authentication Overview.

IAM Permissions

Requires the following IAM permission on the name resource:

  • aiplatform.models.update

For more information, see the IAM documentation.