2026-10-22
▼ ▲ compute.globalFolderOperations.get
Path : {+folder}/global/operations/{operation}
Parameter Order :
Description : Retrieves the specified Operations resource.
Flat Path : folders/{foldersId}/global/operations/{operation}
HTTP Method : GET
Scopes :
Parameters :
operation
Required : Yes
Type : string
Location : path
Description : Name of the Operations resource to return.
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?|[1-9][0-9]{0,19}
folder
Description : Folder ID for this request.
Required : Yes
Location : path
Type : string
Pattern : folders/[0-9]{0,20}
Apiversion : 2026-10-01-preview
▼ ▲ compute.globalFolderOperations.list
Flat Path : folders/{foldersId}/global/operations
Scopes :
Parameter Order : folder
Apiversion : 2026-10-01-preview
Parameters :
folder
Required : Yes
Location : path
Description : Folder ID for this request.
Type : string
Pattern : folders/[0-9]{0,20}
orderBy
Description : Sorts list results by a certain order. By default, results are returned in alphanumerical order based on the resource name. You can also sort results in descending order based on the creation timestamp using `orderBy="creationTimestamp desc"`. This sorts results based on the `creationTimestamp` field in reverse chronological order (newest result first). Use this to sort resources like operations so that the newest operation is returned first. Currently, only sorting by `name` or `creationTimestamp desc` is supported.
Location : query
Type : string
pageToken
Location : query
Type : string
Description : Specifies a page token to use. Set `pageToken` to the `nextPageToken` returned by a previous list request to get the next page of results.
maxResults
Type : integer
Default : 500
Format : uint32
Minimum : 0
Location : query
Description : The maximum number of results per page that should be returned. If the number of available results is larger than `maxResults`, Compute Engine returns a `nextPageToken` that can be used to get the next page of results in subsequent list requests. Acceptable values are `0` to `500`, inclusive. (Default: `500`)
filter
Type : string
Description : A filter expression that filters resources listed in the response. Most Compute resources support two types of filter expressions: expressions that support regular expressions and expressions that follow API improvement proposal AIP-160. These two types of filter expressions cannot be mixed in one request. If you want to use AIP-160, your expression must specify the field name, an operator, and the value that you want to use for filtering. The value must be a string, a number, or a boolean. The operator must be either `=`, `!=`, `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute Engine instances, you can exclude instances named `example-instance` by specifying `name != example-instance`. The `:*` comparison can be used to test whether a key has been defined. For example, to find all objects with `owner` label use: ``` labels.owner:* ``` You can also filter nested fields. For example, you could specify `scheduling.automaticRestart = false` to include instances only if they are not scheduled for automatic restarts. You can use filtering on nested fields to filter based onresource labels. To filter on multiple expressions, provide each separate expression within parentheses. For example: ``` (scheduling.automaticRestart = true) (cpuPlatform = "Intel Skylake") ``` By default, each expression is an `AND` expression. However, you can include `AND` and `OR` expressions explicitly. For example: ``` (cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.automaticRestart = true) ``` If you want to use a regular expression, use the `eq` (equal) or `ne` (not equal) operator against a single un-parenthesized expression with or without quotes or against multiple parenthesized expressions. Examples: `fieldname eq unquoted literal` `fieldname eq 'single quoted literal'` `fieldname eq "double quoted literal"` `(fieldname1 eq literal) (fieldname2 ne "literal")` The literal value is interpreted as a regular expression using GoogleRE2 library syntax. The literal value must match the entire field. For example, to filter for instances that do not end with name "instance", you would use `name ne .*instance`. You cannot combine constraints on multiple fields using regular expressions.
Location : query
Path : {+folder}/global/operations
Description : Retrieves a list of Operation resources contained within the specified folder.
HTTP Method : GET
▼ ▲ compute.folderGlobalVmExtensionPolicies.delete
Path : {+folder}/global/vmExtensionPolicies/{globalVmExtensionPolicy}/delete
Parameter Order :
HTTP Method : POST
Flat Path : folders/{foldersId}/global/vmExtensionPolicies/{globalVmExtensionPolicy}/delete
Apiversion : 2026-10-01-preview
Parameters :
folder
Type : string
Description : Folder ID for this request.
Pattern : folders/[0-9]{0,20}
Location : path
Required : Yes
globalVmExtensionPolicy
Description : Name of the global VM extension policy to purge scoped resources for.
Location : path
Required : Yes
Type : string
requestId
Location : query
Type : string
Description : An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments. The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000).
Description : Purge scoped resources (zonal policies) from a folder level global VM extension policy, and then delete the global VM extension policy. Purge of the scoped resources is a pre-condition of the global VM extension policy deletion. The deletion of the global VM extension policy happens after the purge rollout is done, so it's not a part of the LRO. It's an automatic process that triggers in the backend.
Scopes :
▼ ▲ compute.folderGlobalVmExtensionPolicies.listVmExtensions
Flat Path : folders/{foldersId}/global/vmExtensions
Parameter Order : folder
Scopes :
HTTP Method : GET
Description : Lists all VM extensions within a folder. This is a read-only API.
Parameters :
pageToken
Description : Specifies a page token to use. Set `pageToken` to the `nextPageToken` returned by a previous list request to get the next page of results.
Location : query
Type : string
orderBy
Location : query
Description : Sorts list results by a certain order. By default, results are returned in alphanumerical order based on the resource name. You can also sort results in descending order based on the creation timestamp using `orderBy="creationTimestamp desc"`. This sorts results based on the `creationTimestamp` field in reverse chronological order (newest result first). Use this to sort resources like operations so that the newest operation is returned first. Currently, only sorting by `name` or `creationTimestamp desc` is supported.
Type : string
filter
Location : query
Type : string
Description : A filter expression that filters resources listed in the response. Most Compute resources support two types of filter expressions: expressions that support regular expressions and expressions that follow API improvement proposal AIP-160. These two types of filter expressions cannot be mixed in one request. If you want to use AIP-160, your expression must specify the field name, an operator, and the value that you want to use for filtering. The value must be a string, a number, or a boolean. The operator must be either `=`, `!=`, `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute Engine instances, you can exclude instances named `example-instance` by specifying `name != example-instance`. The `:*` comparison can be used to test whether a key has been defined. For example, to find all objects with `owner` label use: ``` labels.owner:* ``` You can also filter nested fields. For example, you could specify `scheduling.automaticRestart = false` to include instances only if they are not scheduled for automatic restarts. You can use filtering on nested fields to filter based onresource labels. To filter on multiple expressions, provide each separate expression within parentheses. For example: ``` (scheduling.automaticRestart = true) (cpuPlatform = "Intel Skylake") ``` By default, each expression is an `AND` expression. However, you can include `AND` and `OR` expressions explicitly. For example: ``` (cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.automaticRestart = true) ``` If you want to use a regular expression, use the `eq` (equal) or `ne` (not equal) operator against a single un-parenthesized expression with or without quotes or against multiple parenthesized expressions. Examples: `fieldname eq unquoted literal` `fieldname eq 'single quoted literal'` `fieldname eq "double quoted literal"` `(fieldname1 eq literal) (fieldname2 ne "literal")` The literal value is interpreted as a regular expression using GoogleRE2 library syntax. The literal value must match the entire field. For example, to filter for instances that do not end with name "instance", you would use `name ne .*instance`. You cannot combine constraints on multiple fields using regular expressions.
maxResults
Default : 500
Description : The maximum number of results per page that should be returned. If the number of available results is larger than `maxResults`, Compute Engine returns a `nextPageToken` that can be used to get the next page of results in subsequent list requests. Acceptable values are `0` to `500`, inclusive. (Default: `500`)
Minimum : 0
Location : query
Type : integer
Format : uint32
folder
Type : string
Required : Yes
Description : Required. Folder ID for this request.
Location : path
Pattern : folders/[0-9]{0,20}
Apiversion : 2026-10-01-preview
Path : {+folder}/global/vmExtensions
▼ ▲ compute.folderGlobalVmExtensionPolicies.get
Apiversion : 2026-10-01-preview
Parameters :
folder
Type : string
Required : Yes
Location : path
Description : Folder ID for this request.
Pattern : folders/[0-9]{0,20}
globalVmExtensionPolicy
Type : string
Location : path
Required : Yes
Description : Name of the GlobalVmExtensionPolicy resource to return.
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?|[1-9][0-9]{0,19}
Parameter Order :
HTTP Method : GET
Path : {+folder}/global/vmExtensionPolicies/{globalVmExtensionPolicy}
Scopes :
Description : Gets details of a folder level GlobalVmExtensionPolicy.
Flat Path : folders/{foldersId}/global/vmExtensionPolicies/{globalVmExtensionPolicy}
▼ ▲ compute.folderGlobalVmExtensionPolicies.list
Apiversion : 2026-10-01-preview
Parameters :
maxResults
Location : query
Format : uint32
Description : The maximum number of results per page that should be returned. If the number of available results is larger than `maxResults`, Compute Engine returns a `nextPageToken` that can be used to get the next page of results in subsequent list requests. Acceptable values are `0` to `500`, inclusive. (Default: `500`)
Type : integer
Default : 500
Minimum : 0
orderBy
Type : string
Description : Sorts list results by a certain order. By default, results are returned in alphanumerical order based on the resource name. You can also sort results in descending order based on the creation timestamp using `orderBy="creationTimestamp desc"`. This sorts results based on the `creationTimestamp` field in reverse chronological order (newest result first). Use this to sort resources like operations so that the newest operation is returned first. Currently, only sorting by `name` or `creationTimestamp desc` is supported.
Location : query
pageToken
Location : query
Type : string
Description : Specifies a page token to use. Set `pageToken` to the `nextPageToken` returned by a previous list request to get the next page of results.
filter
Description : A filter expression that filters resources listed in the response. Most Compute resources support two types of filter expressions: expressions that support regular expressions and expressions that follow API improvement proposal AIP-160. These two types of filter expressions cannot be mixed in one request. If you want to use AIP-160, your expression must specify the field name, an operator, and the value that you want to use for filtering. The value must be a string, a number, or a boolean. The operator must be either `=`, `!=`, `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute Engine instances, you can exclude instances named `example-instance` by specifying `name != example-instance`. The `:*` comparison can be used to test whether a key has been defined. For example, to find all objects with `owner` label use: ``` labels.owner:* ``` You can also filter nested fields. For example, you could specify `scheduling.automaticRestart = false` to include instances only if they are not scheduled for automatic restarts. You can use filtering on nested fields to filter based onresource labels. To filter on multiple expressions, provide each separate expression within parentheses. For example: ``` (scheduling.automaticRestart = true) (cpuPlatform = "Intel Skylake") ``` By default, each expression is an `AND` expression. However, you can include `AND` and `OR` expressions explicitly. For example: ``` (cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.automaticRestart = true) ``` If you want to use a regular expression, use the `eq` (equal) or `ne` (not equal) operator against a single un-parenthesized expression with or without quotes or against multiple parenthesized expressions. Examples: `fieldname eq unquoted literal` `fieldname eq 'single quoted literal'` `fieldname eq "double quoted literal"` `(fieldname1 eq literal) (fieldname2 ne "literal")` The literal value is interpreted as a regular expression using GoogleRE2 library syntax. The literal value must match the entire field. For example, to filter for instances that do not end with name "instance", you would use `name ne .*instance`. You cannot combine constraints on multiple fields using regular expressions.
Type : string
Location : query
folder
Pattern : folders/[0-9]{0,20}
Description : Folder ID for this request.
Location : path
Type : string
Required : Yes
Scopes :
Description : Lists folder level GlobalVmExtensionPolicies.
Flat Path : folders/{foldersId}/global/vmExtensionPolicies
HTTP Method : GET
Parameter Order : folder
Path : {+folder}/global/vmExtensionPolicies
▼ ▲ compute.folderGlobalVmExtensionPolicies.update
HTTP Method : PATCH
Path : {+folder}/global/vmExtensionPolicies/{globalVmExtensionPolicy}
Scopes :
Apiversion : 2026-10-01-preview
Parameters :
globalVmExtensionPolicy
Required : Yes
Type : string
Description : Name of the global VM extension policy to update.
Location : path
folder
Description : Folder ID for this request.
Pattern : folders/[0-9]{0,20}
Location : path
Required : Yes
Type : string
requestId
Description : An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments. The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000).
Location : query
Type : string
Parameter Order :
Flat Path : folders/{foldersId}/global/vmExtensionPolicies/{globalVmExtensionPolicy}
Description : Updates a folder level GlobalVmExtensionPolicy.
▼ ▲ compute.folderGlobalVmExtensionPolicies.getVmExtension
HTTP Method : GET
Description : Retrieves details of a specific VM extension.
Flat Path : folders/{foldersId}/global/vmExtensions/{extensionName}
Parameters :
extensionName
Type : string
Required : Yes
Location : path
Description : Required. Name of the VM extension for this request.
folder
Pattern : folders/[0-9]{0,20}
Location : path
Required : Yes
Description : Folder ID for this request.
Type : string
Apiversion : 2026-10-01-preview
Scopes :
Parameter Order :
Path : {+folder}/global/vmExtensions/{extensionName}
▼ ▲ compute.folderGlobalVmExtensionPolicies.aggregatedList
Description : Retrieves the list of all folder level VM Extension Policy resources available to the specified folder. To prevent failure, it's recommended that you set the `returnPartialSuccess` parameter to `true`.
Parameter Order : folder
Scopes :
Flat Path : folders/{foldersId}/aggregated/vmExtensionPolicies
Path : {+folder}/aggregated/vmExtensionPolicies
HTTP Method : GET
Apiversion : 2026-10-01-preview
Parameters :
filter
Location : query
Type : string
Description : A filter expression that filters resources listed in the response. Most Compute resources support two types of filter expressions: expressions that support regular expressions and expressions that follow API improvement proposal AIP-160. These two types of filter expressions cannot be mixed in one request. If you want to use AIP-160, your expression must specify the field name, an operator, and the value that you want to use for filtering. The value must be a string, a number, or a boolean. The operator must be either `=`, `!=`, `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute Engine instances, you can exclude instances named `example-instance` by specifying `name != example-instance`. The `:*` comparison can be used to test whether a key has been defined. For example, to find all objects with `owner` label use: ``` labels.owner:* ``` You can also filter nested fields. For example, you could specify `scheduling.automaticRestart = false` to include instances only if they are not scheduled for automatic restarts. You can use filtering on nested fields to filter based onresource labels. To filter on multiple expressions, provide each separate expression within parentheses. For example: ``` (scheduling.automaticRestart = true) (cpuPlatform = "Intel Skylake") ``` By default, each expression is an `AND` expression. However, you can include `AND` and `OR` expressions explicitly. For example: ``` (cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.automaticRestart = true) ``` If you want to use a regular expression, use the `eq` (equal) or `ne` (not equal) operator against a single un-parenthesized expression with or without quotes or against multiple parenthesized expressions. Examples: `fieldname eq unquoted literal` `fieldname eq 'single quoted literal'` `fieldname eq "double quoted literal"` `(fieldname1 eq literal) (fieldname2 ne "literal")` The literal value is interpreted as a regular expression using GoogleRE2 library syntax. The literal value must match the entire field. For example, to filter for instances that do not end with name "instance", you would use `name ne .*instance`. You cannot combine constraints on multiple fields using regular expressions.
pageToken
Location : query
Description : Specifies a page token to use. Set `pageToken` to the `nextPageToken` returned by a previous list request to get the next page of results.
Type : string
includeAllScopes
Description : Indicates whether every visible scope for each scope type (zone, region, global) should be included in the response. For new resource types added after this field, the flag has no effect as new resource types will always include every visible scope for each scope type in response. For resource types which predate this field, if this flag is omitted or false, only scopes of the scope types where the resource type is expected to be found will be included.
Type : boolean
Location : query
orderBy
Type : string
Description : Sorts list results by a certain order. By default, results are returned in alphanumerical order based on the resource name. You can also sort results in descending order based on the creation timestamp using `orderBy="creationTimestamp desc"`. This sorts results based on the `creationTimestamp` field in reverse chronological order (newest result first). Use this to sort resources like operations so that the newest operation is returned first. Currently, only sorting by `name` or `creationTimestamp desc` is supported.
Location : query
folder
Required : Yes
Location : path
Pattern : folders/[0-9]{0,20}
Type : string
Description : Folder ID for this request.
maxResults
Format : uint32
Location : query
Minimum : 0
Type : integer
Default : 500
Description : The maximum number of results per page that should be returned. If the number of available results is larger than `maxResults`, Compute Engine returns a `nextPageToken` that can be used to get the next page of results in subsequent list requests. Acceptable values are `0` to `500`, inclusive. (Default: `500`)
serviceProjectNumber
Format : int64
Type : string
Description : The Shared VPC service project id or service project number for which aggregated list request is invoked for subnetworks list-usable api.
Location : query
▼ ▲ compute.folderGlobalVmExtensionPolicies.insert
Parameter Order : folder
Apiversion : 2026-10-01-preview
Parameters :
folder
Pattern : folders/[0-9]{0,20}
Type : string
Location : path
Description : Folder ID for this request.
Required : Yes
requestId
Description : An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments. The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000).
Location : query
Type : string
Flat Path : folders/{foldersId}/global/vmExtensionPolicies
Description : Creates a new folder level GlobalVmExtensionPolicy.
Scopes :
HTTP Method : POST
Path : {+folder}/global/vmExtensionPolicies
▼ ▲ compute.organizationGlobalVmExtensionPolicies.insert
Description : Creates a new organization level GlobalVmExtensionPolicy.
Scopes :
Parameters :
requestId
Location : query
Description : An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments. The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000).
Type : string
organization
Required : Yes
Type : string
Location : path
Pattern : organizations/[0-9]{0,20}
Description : Organization ID for this request.
Apiversion : 2026-10-01-preview
Flat Path : organizations/{organizationsId}/global/vmExtensionPolicies
HTTP Method : POST
Path : {+organization}/global/vmExtensionPolicies
Parameter Order : organization
▼ ▲ compute.organizationGlobalVmExtensionPolicies.listVmExtensions
Parameters :
pageToken
Description : Specifies a page token to use. Set `pageToken` to the `nextPageToken` returned by a previous list request to get the next page of results.
Location : query
Type : string
organization
Type : string
Required : Yes
Location : path
Description : Required. Organization ID for this request.
Pattern : organizations/[0-9]{0,20}
filter
Description : A filter expression that filters resources listed in the response. Most Compute resources support two types of filter expressions: expressions that support regular expressions and expressions that follow API improvement proposal AIP-160. These two types of filter expressions cannot be mixed in one request. If you want to use AIP-160, your expression must specify the field name, an operator, and the value that you want to use for filtering. The value must be a string, a number, or a boolean. The operator must be either `=`, `!=`, `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute Engine instances, you can exclude instances named `example-instance` by specifying `name != example-instance`. The `:*` comparison can be used to test whether a key has been defined. For example, to find all objects with `owner` label use: ``` labels.owner:* ``` You can also filter nested fields. For example, you could specify `scheduling.automaticRestart = false` to include instances only if they are not scheduled for automatic restarts. You can use filtering on nested fields to filter based onresource labels. To filter on multiple expressions, provide each separate expression within parentheses. For example: ``` (scheduling.automaticRestart = true) (cpuPlatform = "Intel Skylake") ``` By default, each expression is an `AND` expression. However, you can include `AND` and `OR` expressions explicitly. For example: ``` (cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.automaticRestart = true) ``` If you want to use a regular expression, use the `eq` (equal) or `ne` (not equal) operator against a single un-parenthesized expression with or without quotes or against multiple parenthesized expressions. Examples: `fieldname eq unquoted literal` `fieldname eq 'single quoted literal'` `fieldname eq "double quoted literal"` `(fieldname1 eq literal) (fieldname2 ne "literal")` The literal value is interpreted as a regular expression using GoogleRE2 library syntax. The literal value must match the entire field. For example, to filter for instances that do not end with name "instance", you would use `name ne .*instance`. You cannot combine constraints on multiple fields using regular expressions.
Type : string
Location : query
orderBy
Description : Sorts list results by a certain order. By default, results are returned in alphanumerical order based on the resource name. You can also sort results in descending order based on the creation timestamp using `orderBy="creationTimestamp desc"`. This sorts results based on the `creationTimestamp` field in reverse chronological order (newest result first). Use this to sort resources like operations so that the newest operation is returned first. Currently, only sorting by `name` or `creationTimestamp desc` is supported.
Location : query
Type : string
maxResults
Format : uint32
Type : integer
Description : The maximum number of results per page that should be returned. If the number of available results is larger than `maxResults`, Compute Engine returns a `nextPageToken` that can be used to get the next page of results in subsequent list requests. Acceptable values are `0` to `500`, inclusive. (Default: `500`)
Location : query
Default : 500
Minimum : 0
Flat Path : organizations/{organizationsId}/global/vmExtensions
Scopes :
Apiversion : 2026-10-01-preview
HTTP Method : GET
Path : {+organization}/global/vmExtensions
Parameter Order : organization
Description : Lists all VM extensions within an organization. This is a read-only API.
▼ ▲ compute.organizationGlobalVmExtensionPolicies.list
Parameter Order : organization
Scopes :
Apiversion : 2026-10-01-preview
Path : {+organization}/global/vmExtensionPolicies
Parameters :
orderBy
Type : string
Description : Sorts list results by a certain order. By default, results are returned in alphanumerical order based on the resource name. You can also sort results in descending order based on the creation timestamp using `orderBy="creationTimestamp desc"`. This sorts results based on the `creationTimestamp` field in reverse chronological order (newest result first). Use this to sort resources like operations so that the newest operation is returned first. Currently, only sorting by `name` or `creationTimestamp desc` is supported.
Location : query
organization
Description : Organization ID for this request.
Pattern : organizations/[0-9]{0,20}
Required : Yes
Location : path
Type : string
filter
Description : A filter expression that filters resources listed in the response. Most Compute resources support two types of filter expressions: expressions that support regular expressions and expressions that follow API improvement proposal AIP-160. These two types of filter expressions cannot be mixed in one request. If you want to use AIP-160, your expression must specify the field name, an operator, and the value that you want to use for filtering. The value must be a string, a number, or a boolean. The operator must be either `=`, `!=`, `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute Engine instances, you can exclude instances named `example-instance` by specifying `name != example-instance`. The `:*` comparison can be used to test whether a key has been defined. For example, to find all objects with `owner` label use: ``` labels.owner:* ``` You can also filter nested fields. For example, you could specify `scheduling.automaticRestart = false` to include instances only if they are not scheduled for automatic restarts. You can use filtering on nested fields to filter based onresource labels. To filter on multiple expressions, provide each separate expression within parentheses. For example: ``` (scheduling.automaticRestart = true) (cpuPlatform = "Intel Skylake") ``` By default, each expression is an `AND` expression. However, you can include `AND` and `OR` expressions explicitly. For example: ``` (cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.automaticRestart = true) ``` If you want to use a regular expression, use the `eq` (equal) or `ne` (not equal) operator against a single un-parenthesized expression with or without quotes or against multiple parenthesized expressions. Examples: `fieldname eq unquoted literal` `fieldname eq 'single quoted literal'` `fieldname eq "double quoted literal"` `(fieldname1 eq literal) (fieldname2 ne "literal")` The literal value is interpreted as a regular expression using GoogleRE2 library syntax. The literal value must match the entire field. For example, to filter for instances that do not end with name "instance", you would use `name ne .*instance`. You cannot combine constraints on multiple fields using regular expressions.
Location : query
Type : string
pageToken
Description : Specifies a page token to use. Set `pageToken` to the `nextPageToken` returned by a previous list request to get the next page of results.
Location : query
Type : string
maxResults
Location : query
Format : uint32
Type : integer
Description : The maximum number of results per page that should be returned. If the number of available results is larger than `maxResults`, Compute Engine returns a `nextPageToken` that can be used to get the next page of results in subsequent list requests. Acceptable values are `0` to `500`, inclusive. (Default: `500`)
Default : 500
Minimum : 0
Description : Lists organization level GlobalVmExtensionPolicies.
HTTP Method : GET
Flat Path : organizations/{organizationsId}/global/vmExtensionPolicies
▼ ▲ compute.organizationGlobalVmExtensionPolicies.aggregatedList
HTTP Method : GET
Parameters :
includeAllScopes
Type : boolean
Location : query
Description : Indicates whether every visible scope for each scope type (zone, region, global) should be included in the response. For new resource types added after this field, the flag has no effect as new resource types will always include every visible scope for each scope type in response. For resource types which predate this field, if this flag is omitted or false, only scopes of the scope types where the resource type is expected to be found will be included.
filter
Location : query
Type : string
Description : A filter expression that filters resources listed in the response. Most Compute resources support two types of filter expressions: expressions that support regular expressions and expressions that follow API improvement proposal AIP-160. These two types of filter expressions cannot be mixed in one request. If you want to use AIP-160, your expression must specify the field name, an operator, and the value that you want to use for filtering. The value must be a string, a number, or a boolean. The operator must be either `=`, `!=`, `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute Engine instances, you can exclude instances named `example-instance` by specifying `name != example-instance`. The `:*` comparison can be used to test whether a key has been defined. For example, to find all objects with `owner` label use: ``` labels.owner:* ``` You can also filter nested fields. For example, you could specify `scheduling.automaticRestart = false` to include instances only if they are not scheduled for automatic restarts. You can use filtering on nested fields to filter based onresource labels. To filter on multiple expressions, provide each separate expression within parentheses. For example: ``` (scheduling.automaticRestart = true) (cpuPlatform = "Intel Skylake") ``` By default, each expression is an `AND` expression. However, you can include `AND` and `OR` expressions explicitly. For example: ``` (cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.automaticRestart = true) ``` If you want to use a regular expression, use the `eq` (equal) or `ne` (not equal) operator against a single un-parenthesized expression with or without quotes or against multiple parenthesized expressions. Examples: `fieldname eq unquoted literal` `fieldname eq 'single quoted literal'` `fieldname eq "double quoted literal"` `(fieldname1 eq literal) (fieldname2 ne "literal")` The literal value is interpreted as a regular expression using GoogleRE2 library syntax. The literal value must match the entire field. For example, to filter for instances that do not end with name "instance", you would use `name ne .*instance`. You cannot combine constraints on multiple fields using regular expressions.
pageToken
Location : query
Type : string
Description : Specifies a page token to use. Set `pageToken` to the `nextPageToken` returned by a previous list request to get the next page of results.
orderBy
Location : query
Description : Sorts list results by a certain order. By default, results are returned in alphanumerical order based on the resource name. You can also sort results in descending order based on the creation timestamp using `orderBy="creationTimestamp desc"`. This sorts results based on the `creationTimestamp` field in reverse chronological order (newest result first). Use this to sort resources like operations so that the newest operation is returned first. Currently, only sorting by `name` or `creationTimestamp desc` is supported.
Type : string
maxResults
Default : 500
Type : integer
Description : The maximum number of results per page that should be returned. If the number of available results is larger than `maxResults`, Compute Engine returns a `nextPageToken` that can be used to get the next page of results in subsequent list requests. Acceptable values are `0` to `500`, inclusive. (Default: `500`)
Minimum : 0
Location : query
Format : uint32
organization
Description : Organization ID for this request.
Pattern : organizations/[0-9]{0,20}
Location : path
Required : Yes
Type : string
serviceProjectNumber
Location : query
Type : string
Format : int64
Description : The Shared VPC service project id or service project number for which aggregated list request is invoked for subnetworks list-usable api.
Apiversion : 2026-10-01-preview
Path : {+organization}/aggregated/vmExtensionPolicies
Scopes :
Parameter Order : organization
Description : Retrieves the list of all organization level VM Extension Policy resources available to the specified organization. To prevent failure, it's recommended that you set the `returnPartialSuccess` parameter to `true`.
Flat Path : organizations/{organizationsId}/aggregated/vmExtensionPolicies
▼ ▲ compute.organizationGlobalVmExtensionPolicies.update
Scopes :
HTTP Method : PATCH
Path : {+organization}/global/vmExtensionPolicies/{globalVmExtensionPolicy}
Parameters :
requestId
Location : query
Type : string
Description : An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments. The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000).
organization
Pattern : organizations/[0-9]{0,20}
Location : path
Required : Yes
Type : string
Description : Organization ID for this request.
globalVmExtensionPolicy
Required : Yes
Type : string
Location : path
Description : Name of the global VM extension policy to update.
Apiversion : 2026-10-01-preview
Flat Path : organizations/{organizationsId}/global/vmExtensionPolicies/{globalVmExtensionPolicy}
Parameter Order :
Description : Updates an organization level GlobalVmExtensionPolicy.
▼ ▲ compute.organizationGlobalVmExtensionPolicies.get
Path : {+organization}/global/vmExtensionPolicies/{globalVmExtensionPolicy}
Scopes :
Flat Path : organizations/{organizationsId}/global/vmExtensionPolicies/{globalVmExtensionPolicy}
HTTP Method : GET
Description : Gets details of an organization level GlobalVmExtensionPolicy.
Parameter Order :
Parameters :
globalVmExtensionPolicy
Required : Yes
Description : Name of the GlobalVmExtensionPolicy resource to return.
Location : path
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?|[1-9][0-9]{0,19}
Type : string
organization
Location : path
Pattern : organizations/[0-9]{0,20}
Required : Yes
Type : string
Description : Organization ID for this request.
Apiversion : 2026-10-01-preview
▼ ▲ compute.organizationGlobalVmExtensionPolicies.delete
Scopes :
Parameter Order :
Flat Path : organizations/{organizationsId}/global/vmExtensionPolicies/{globalVmExtensionPolicy}/delete
Path : {+organization}/global/vmExtensionPolicies/{globalVmExtensionPolicy}/delete
Description : Purge scoped resources (zonal policies) from an organization level global VM extension policy, and then delete the global VM extension policy. Purge of the scoped resources is a pre-condition of the global VM extension policy deletion. The deletion of the global VM extension policy happens after the purge rollout is done, so it's not a part of the LRO. It's an automatic process that triggers in the backend.
HTTP Method : POST
Parameters :
organization
Pattern : organizations/[0-9]{0,20}
Location : path
Required : Yes
Type : string
Description : Organization ID for this request.
requestId
Type : string
Description : An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments. The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000).
Location : query
globalVmExtensionPolicy
Description : Name of the global VM extension policy to purge scoped resources for.
Required : Yes
Type : string
Location : path
Apiversion : 2026-10-01-preview
▼ ▲ compute.organizationGlobalVmExtensionPolicies.getVmExtension
HTTP Method : GET
Parameters :
organization
Description : Organization ID for this request.
Type : string
Required : Yes
Pattern : organizations/[0-9]{0,20}
Location : path
extensionName
Required : Yes
Type : string
Location : path
Description : Required. Name of the VM extension for this request.
Apiversion : 2026-10-01-preview
Flat Path : organizations/{organizationsId}/global/vmExtensions/{extensionName}
Description : Retrieves details of a specific VM extension.
Scopes :
Parameter Order :
Path : {+organization}/global/vmExtensions/{extensionName}
▼ ▲ compute.zoneFolderOperations.list
HTTP Method : GET
Flat Path : folders/{foldersId}/zones/{zone}/operations
Apiversion : 2026-10-01-preview
Parameters :
folder
Required : Yes
Type : string
Location : path
Pattern : folders/[0-9]{0,20}
Description : Folder ID for this request.
pageToken
Location : query
Description : Specifies a page token to use. Set `pageToken` to the `nextPageToken` returned by a previous list request to get the next page of results.
Type : string
filter
Type : string
Location : query
Description : A filter expression that filters resources listed in the response. Most Compute resources support two types of filter expressions: expressions that support regular expressions and expressions that follow API improvement proposal AIP-160. These two types of filter expressions cannot be mixed in one request. If you want to use AIP-160, your expression must specify the field name, an operator, and the value that you want to use for filtering. The value must be a string, a number, or a boolean. The operator must be either `=`, `!=`, `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute Engine instances, you can exclude instances named `example-instance` by specifying `name != example-instance`. The `:*` comparison can be used to test whether a key has been defined. For example, to find all objects with `owner` label use: ``` labels.owner:* ``` You can also filter nested fields. For example, you could specify `scheduling.automaticRestart = false` to include instances only if they are not scheduled for automatic restarts. You can use filtering on nested fields to filter based onresource labels. To filter on multiple expressions, provide each separate expression within parentheses. For example: ``` (scheduling.automaticRestart = true) (cpuPlatform = "Intel Skylake") ``` By default, each expression is an `AND` expression. However, you can include `AND` and `OR` expressions explicitly. For example: ``` (cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.automaticRestart = true) ``` If you want to use a regular expression, use the `eq` (equal) or `ne` (not equal) operator against a single un-parenthesized expression with or without quotes or against multiple parenthesized expressions. Examples: `fieldname eq unquoted literal` `fieldname eq 'single quoted literal'` `fieldname eq "double quoted literal"` `(fieldname1 eq literal) (fieldname2 ne "literal")` The literal value is interpreted as a regular expression using GoogleRE2 library syntax. The literal value must match the entire field. For example, to filter for instances that do not end with name "instance", you would use `name ne .*instance`. You cannot combine constraints on multiple fields using regular expressions.
zone
Description : Name of the zone for request.
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
Type : string
Location : path
Required : Yes
orderBy
Description : Sorts list results by a certain order. By default, results are returned in alphanumerical order based on the resource name. You can also sort results in descending order based on the creation timestamp using `orderBy="creationTimestamp desc"`. This sorts results based on the `creationTimestamp` field in reverse chronological order (newest result first). Use this to sort resources like operations so that the newest operation is returned first. Currently, only sorting by `name` or `creationTimestamp desc` is supported.
Location : query
Type : string
maxResults
Type : integer
Description : The maximum number of results per page that should be returned. If the number of available results is larger than `maxResults`, Compute Engine returns a `nextPageToken` that can be used to get the next page of results in subsequent list requests. Acceptable values are `0` to `500`, inclusive. (Default: `500`)
Location : query
Default : 500
Format : uint32
Minimum : 0
Scopes :
Parameter Order :
Path : {+folder}/zones/{zone}/operations
Description : Retrieves a list of Operation resources contained within the specified folder.
▼ ▲ compute.zoneFolderOperations.get
HTTP Method : GET
Description : Retrieves the specified Operations resource.
Flat Path : folders/{foldersId}/zones/{zone}/operations/{operation}
Apiversion : 2026-10-01-preview
Scopes :
Parameter Order :
Parameters :
operation
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?|[1-9][0-9]{0,19}
Type : string
Location : path
Required : Yes
Description : Name of the Operations resource to return.
zone
Type : string
Description : Name of the zone for this request.
Location : path
Required : Yes
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
folder
Location : path
Pattern : folders/[0-9]{0,20}
Required : Yes
Description : Folder ID for this request.
Type : string
Path : {+folder}/zones/{zone}/operations/{operation}
▼ ▲ compute.zoneVmExtensionPolicies.listVmExtensions
Description : Lists all VM extensions within a specific zone for a project. This is a read-only API.
Parameter Order :
HTTP Method : GET
Path : projects/{project}/zones/{zone}/vmExtensions
Apiversion : 2026-10-01-preview
Scopes :
Parameters :
filter
Description : A filter expression that filters resources listed in the response. Most Compute resources support two types of filter expressions: expressions that support regular expressions and expressions that follow API improvement proposal AIP-160. These two types of filter expressions cannot be mixed in one request. If you want to use AIP-160, your expression must specify the field name, an operator, and the value that you want to use for filtering. The value must be a string, a number, or a boolean. The operator must be either `=`, `!=`, `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute Engine instances, you can exclude instances named `example-instance` by specifying `name != example-instance`. The `:*` comparison can be used to test whether a key has been defined. For example, to find all objects with `owner` label use: ``` labels.owner:* ``` You can also filter nested fields. For example, you could specify `scheduling.automaticRestart = false` to include instances only if they are not scheduled for automatic restarts. You can use filtering on nested fields to filter based onresource labels. To filter on multiple expressions, provide each separate expression within parentheses. For example: ``` (scheduling.automaticRestart = true) (cpuPlatform = "Intel Skylake") ``` By default, each expression is an `AND` expression. However, you can include `AND` and `OR` expressions explicitly. For example: ``` (cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.automaticRestart = true) ``` If you want to use a regular expression, use the `eq` (equal) or `ne` (not equal) operator against a single un-parenthesized expression with or without quotes or against multiple parenthesized expressions. Examples: `fieldname eq unquoted literal` `fieldname eq 'single quoted literal'` `fieldname eq "double quoted literal"` `(fieldname1 eq literal) (fieldname2 ne "literal")` The literal value is interpreted as a regular expression using GoogleRE2 library syntax. The literal value must match the entire field. For example, to filter for instances that do not end with name "instance", you would use `name ne .*instance`. You cannot combine constraints on multiple fields using regular expressions.
Type : string
Location : query
orderBy
Description : Sorts list results by a certain order. By default, results are returned in alphanumerical order based on the resource name. You can also sort results in descending order based on the creation timestamp using `orderBy="creationTimestamp desc"`. This sorts results based on the `creationTimestamp` field in reverse chronological order (newest result first). Use this to sort resources like operations so that the newest operation is returned first. Currently, only sorting by `name` or `creationTimestamp desc` is supported.
Type : string
Location : query
maxResults
Type : integer
Format : uint32
Location : query
Minimum : 0
Default : 500
Description : The maximum number of results per page that should be returned. If the number of available results is larger than `maxResults`, Compute Engine returns a `nextPageToken` that can be used to get the next page of results in subsequent list requests. Acceptable values are `0` to `500`, inclusive. (Default: `500`)
pageToken
Description : Specifies a page token to use. Set `pageToken` to the `nextPageToken` returned by a previous list request to get the next page of results.
Location : query
Type : string
project
Type : string
Pattern : (?:(?:[-a-z0-9]{1,63}\.)*(?:[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?):)?(?:[0-9]{1,19}|(?:[a-z0-9](?:[-a-z0-9]{0,61}[a-z0-9])?))
Description : Required. Project ID for this request.
Location : path
Required : Yes
zone
Description : Name of the zone for this request.
Type : string
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
Location : path
Required : Yes
Flat Path : projects/{project}/zones/{zone}/vmExtensions
▼ ▲ compute.zoneVmExtensionPolicies.getVmExtension
Parameter Order :
HTTP Method : GET
Scopes :
Description : Retrieves details of a specific VM extension within a project.
Apiversion : 2026-10-01-preview
Parameters :
extensionName
Type : string
Description : Required. Name of the VM extension for this request.
Required : Yes
Location : path
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?|[1-9][0-9]{0,19}
project
Required : Yes
Pattern : (?:(?:[-a-z0-9]{1,63}\.)*(?:[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?):)?(?:[0-9]{1,19}|(?:[a-z0-9](?:[-a-z0-9]{0,61}[a-z0-9])?))
Description : Project ID for this request.
Type : string
Location : path
zone
Description : Name of the zone for this request.
Required : Yes
Type : string
Location : path
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
Flat Path : projects/{project}/zones/{zone}/vmExtensions/{extensionName}
Path : projects/{project}/zones/{zone}/vmExtensions/{extensionName}
▼ ▲ compute.folderZoneVmExtensionPolicies.update
Path : {+folder}/zones/{zone}/vmExtensionPolicies/{vmExtensionPolicy}
Flat Path : folders/{foldersId}/zones/{zone}/vmExtensionPolicies/{vmExtensionPolicy}
Parameter Order :
HTTP Method : PATCH
Description : Modifies an existing zone VM extension policy within a folder.
Apiversion : 2026-10-01-preview
Parameters :
zone
Type : string
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
Description : Name of the zone for this request.
Required : Yes
Location : path
folder
Description : Folder ID for this request.
Pattern : folders/[0-9]{0,20}
Type : string
Location : path
Required : Yes
vmExtensionPolicy
Type : string
Location : path
Description : Name of the zone VM extension policy to update.
Required : Yes
requestId
Description : An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments. The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000).
Type : string
Location : query
Scopes :
▼ ▲ compute.folderZoneVmExtensionPolicies.list
Path : {+folder}/zones/{zone}/vmExtensionPolicies
HTTP Method : GET
Scopes :
Parameters :
maxResults
Default : 500
Minimum : 0
Location : query
Format : uint32
Description : The maximum number of results per page that should be returned. If the number of available results is larger than `maxResults`, Compute Engine returns a `nextPageToken` that can be used to get the next page of results in subsequent list requests. Acceptable values are `0` to `500`, inclusive. (Default: `500`)
Type : integer
pageToken
Type : string
Location : query
Description : Specifies a page token to use. Set `pageToken` to the `nextPageToken` returned by a previous list request to get the next page of results.
orderBy
Location : query
Description : Sorts list results by a certain order. By default, results are returned in alphanumerical order based on the resource name. You can also sort results in descending order based on the creation timestamp using `orderBy="creationTimestamp desc"`. This sorts results based on the `creationTimestamp` field in reverse chronological order (newest result first). Use this to sort resources like operations so that the newest operation is returned first. Currently, only sorting by `name` or `creationTimestamp desc` is supported.
Type : string
filter
Description : A filter expression that filters resources listed in the response. Most Compute resources support two types of filter expressions: expressions that support regular expressions and expressions that follow API improvement proposal AIP-160. These two types of filter expressions cannot be mixed in one request. If you want to use AIP-160, your expression must specify the field name, an operator, and the value that you want to use for filtering. The value must be a string, a number, or a boolean. The operator must be either `=`, `!=`, `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute Engine instances, you can exclude instances named `example-instance` by specifying `name != example-instance`. The `:*` comparison can be used to test whether a key has been defined. For example, to find all objects with `owner` label use: ``` labels.owner:* ``` You can also filter nested fields. For example, you could specify `scheduling.automaticRestart = false` to include instances only if they are not scheduled for automatic restarts. You can use filtering on nested fields to filter based onresource labels. To filter on multiple expressions, provide each separate expression within parentheses. For example: ``` (scheduling.automaticRestart = true) (cpuPlatform = "Intel Skylake") ``` By default, each expression is an `AND` expression. However, you can include `AND` and `OR` expressions explicitly. For example: ``` (cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.automaticRestart = true) ``` If you want to use a regular expression, use the `eq` (equal) or `ne` (not equal) operator against a single un-parenthesized expression with or without quotes or against multiple parenthesized expressions. Examples: `fieldname eq unquoted literal` `fieldname eq 'single quoted literal'` `fieldname eq "double quoted literal"` `(fieldname1 eq literal) (fieldname2 ne "literal")` The literal value is interpreted as a regular expression using GoogleRE2 library syntax. The literal value must match the entire field. For example, to filter for instances that do not end with name "instance", you would use `name ne .*instance`. You cannot combine constraints on multiple fields using regular expressions.
Location : query
Type : string
zone
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
Type : string
Location : path
Description : Name of the zone for this request.
Required : Yes
folder
Description : Folder ID for this request.
Type : string
Pattern : folders/[0-9]{0,20}
Required : Yes
Location : path
Description : Lists all VM extension policies within a specific zone for a folder.
Parameter Order :
Flat Path : folders/{foldersId}/zones/{zone}/vmExtensionPolicies
Apiversion : 2026-10-01-preview
▼ ▲ compute.folderZoneVmExtensionPolicies.delete
Description : Deletes a specified zone VM extension policy within a folder.
Flat Path : folders/{foldersId}/zones/{zone}/vmExtensionPolicies/{vmExtensionPolicy}
Parameter Order :
Path : {+folder}/zones/{zone}/vmExtensionPolicies/{vmExtensionPolicy}
Scopes :
Apiversion : 2026-10-01-preview
Parameters :
requestId
Location : query
Description : An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments. The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000).
Type : string
folder
Description : Folder ID for this request.
Type : string
Required : Yes
Pattern : folders/[0-9]{0,20}
Location : path
vmExtensionPolicy
Location : path
Type : string
Description : Name of the zone VM extension policy to delete.
Required : Yes
zone
Location : path
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
Required : Yes
Type : string
Description : Name of the zone for this request.
HTTP Method : DELETE
▼ ▲ compute.folderZoneVmExtensionPolicies.get
Apiversion : 2026-10-01-preview
Parameters :
zone
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
Location : path
Required : Yes
Type : string
Description : Name of the zone for this request.
vmExtensionPolicy
Description : Name of the VM extension policy resource to return.
Required : Yes
Location : path
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?|[1-9][0-9]{0,19}
Type : string
folder
Pattern : folders/[0-9]{0,20}
Description : Folder ID for this request.
Location : path
Required : Yes
Type : string
Scopes :
Description : Retrieves details of a specific zone VM extension policy within a folder.
HTTP Method : GET
Path : {+folder}/zones/{zone}/vmExtensionPolicies/{vmExtensionPolicy}
Flat Path : folders/{foldersId}/zones/{zone}/vmExtensionPolicies/{vmExtensionPolicy}
Parameter Order :
▼ ▲ compute.folderZoneVmExtensionPolicies.listVmExtensions
Scopes :
Description : Lists all VM extensions within a specific zone for a folder. This is a read-only API.
Apiversion : 2026-10-01-preview
Parameters :
zone
Type : string
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
Location : path
Description : Name of the zone for this request.
Required : Yes
folder
Type : string
Required : Yes
Description : Folder ID for this request.
Pattern : folders/[0-9]{0,20}
Location : path
filter
Location : query
Type : string
Description : A filter expression that filters resources listed in the response. Most Compute resources support two types of filter expressions: expressions that support regular expressions and expressions that follow API improvement proposal AIP-160. These two types of filter expressions cannot be mixed in one request. If you want to use AIP-160, your expression must specify the field name, an operator, and the value that you want to use for filtering. The value must be a string, a number, or a boolean. The operator must be either `=`, `!=`, `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute Engine instances, you can exclude instances named `example-instance` by specifying `name != example-instance`. The `:*` comparison can be used to test whether a key has been defined. For example, to find all objects with `owner` label use: ``` labels.owner:* ``` You can also filter nested fields. For example, you could specify `scheduling.automaticRestart = false` to include instances only if they are not scheduled for automatic restarts. You can use filtering on nested fields to filter based onresource labels. To filter on multiple expressions, provide each separate expression within parentheses. For example: ``` (scheduling.automaticRestart = true) (cpuPlatform = "Intel Skylake") ``` By default, each expression is an `AND` expression. However, you can include `AND` and `OR` expressions explicitly. For example: ``` (cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.automaticRestart = true) ``` If you want to use a regular expression, use the `eq` (equal) or `ne` (not equal) operator against a single un-parenthesized expression with or without quotes or against multiple parenthesized expressions. Examples: `fieldname eq unquoted literal` `fieldname eq 'single quoted literal'` `fieldname eq "double quoted literal"` `(fieldname1 eq literal) (fieldname2 ne "literal")` The literal value is interpreted as a regular expression using GoogleRE2 library syntax. The literal value must match the entire field. For example, to filter for instances that do not end with name "instance", you would use `name ne .*instance`. You cannot combine constraints on multiple fields using regular expressions.
maxResults
Description : The maximum number of results per page that should be returned. If the number of available results is larger than `maxResults`, Compute Engine returns a `nextPageToken` that can be used to get the next page of results in subsequent list requests. Acceptable values are `0` to `500`, inclusive. (Default: `500`)
Format : uint32
Location : query
Default : 500
Minimum : 0
Type : integer
pageToken
Description : Specifies a page token to use. Set `pageToken` to the `nextPageToken` returned by a previous list request to get the next page of results.
Location : query
Type : string
orderBy
Location : query
Type : string
Description : Sorts list results by a certain order. By default, results are returned in alphanumerical order based on the resource name. You can also sort results in descending order based on the creation timestamp using `orderBy="creationTimestamp desc"`. This sorts results based on the `creationTimestamp` field in reverse chronological order (newest result first). Use this to sort resources like operations so that the newest operation is returned first. Currently, only sorting by `name` or `creationTimestamp desc` is supported.
Parameter Order :
Path : {+folder}/zones/{zone}/vmExtensions
Flat Path : folders/{foldersId}/zones/{zone}/vmExtensions
HTTP Method : GET
▼ ▲ compute.folderZoneVmExtensionPolicies.getVmExtension
Flat Path : folders/{foldersId}/zones/{zone}/vmExtensions/{extensionName}
Path : {+folder}/zones/{zone}/vmExtensions/{extensionName}
Apiversion : 2026-10-01-preview
Parameters :
extensionName
Type : string
Required : Yes
Location : path
Description : Required. Name of the VM extension for this request.
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?|[1-9][0-9]{0,19}
folder
Type : string
Description : Folder ID for this request.
Required : Yes
Pattern : folders/[0-9]{0,20}
Location : path
zone
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
Description : Name of the zone for this request.
Required : Yes
Type : string
Location : path
Scopes :
HTTP Method : GET
Parameter Order :
Description : Retrieves details of a specific VM extension within a folder.
▼ ▲ compute.folderZoneVmExtensionPolicies.insert
Parameter Order :
Scopes :
Description : Creates a new zone-level VM extension policy within a folder.
Path : {+folder}/zones/{zone}/vmExtensionPolicies
Flat Path : folders/{foldersId}/zones/{zone}/vmExtensionPolicies
HTTP Method : POST
Parameters :
zone
Description : Name of the zone for this request.
Required : Yes
Type : string
Location : path
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
requestId
Description : An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments. The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000).
Location : query
Type : string
folder
Type : string
Pattern : folders/[0-9]{0,20}
Description : Folder ID for this request.
Location : path
Required : Yes
Apiversion : 2026-10-01-preview
▼ ▲ compute.regionSslCertificates.fetchEncryptionKey
Parameter Order :
Description : Returns the public encryption key used to encrypt the TLS private key before upload.
HTTP Method : GET
Path : projects/{project}/regions/{region}/sslCertificates/encryptionKey
Flat Path : projects/{project}/regions/{region}/sslCertificates/encryptionKey
Scopes :
Apiversion : 2026-10-01-preview
Parameters :
region
Description : Name of the region scoping this request.
Required : Yes
Type : string
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
Location : path
project
Required : Yes
Type : string
Pattern : (?:(?:[-a-z0-9]{1,63}\.)*(?:[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?):)?(?:[0-9]{1,19}|(?:[a-z0-9](?:[-a-z0-9]{0,61}[a-z0-9])?))
Description : Project ID for this request.
Location : path
▼ ▲ compute.networks.updateNetworkProfile
Description : Updates the network profile of the specified network. Currently only the following operations are supported: - Removing a Regionally Bound Network Profile
Scopes :
Flat Path : projects/{project}/global/networks/{network}/updateNetworkProfile
Parameter Order :
HTTP Method : POST
Apiversion : 2026-10-01-preview
Path : projects/{project}/global/networks/{network}/updateNetworkProfile
Parameters :
network
Type : string
Description : Name of the network resource to update the network profile for.
Required : Yes
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?|[1-9][0-9]{0,19}
Location : path
requestId
Type : string
Description : An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments. The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000).
Location : query
project
Type : string
Pattern : (?:(?:[-a-z0-9]{1,63}\.)*(?:[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?):)?(?:[0-9]{1,19}|(?:[a-z0-9](?:[-a-z0-9]{0,61}[a-z0-9])?))
Location : path
Description : Project ID for this request.
Required : Yes
▼ ▲ compute.globalVmExtensionPolicies.getVmExtension
Description : Retrieves details of a specific VM extension.
Scopes :
HTTP Method : GET
Parameter Order :
Flat Path : projects/{project}/global/vmExtensions/{extensionName}
Apiversion : 2026-10-01-preview
Path : projects/{project}/global/vmExtensions/{extensionName}
Parameters :
project
Description : Project ID for this request.
Required : Yes
Pattern : (?:(?:[-a-z0-9]{1,63}\.)*(?:[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?):)?(?:[0-9]{1,19}|(?:[a-z0-9](?:[-a-z0-9]{0,61}[a-z0-9])?))
Type : string
Location : path
extensionName
Required : Yes
Location : path
Description : Required. Name of the VM extension for this request.
Type : string
▼ ▲ compute.globalVmExtensionPolicies.listVmExtensions
Flat Path : projects/{project}/global/vmExtensions
HTTP Method : GET
Scopes :
Path : projects/{project}/global/vmExtensions
Parameters :
project
Type : string
Location : path
Pattern : (?:(?:[-a-z0-9]{1,63}\.)*(?:[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?):)?(?:[0-9]{1,19}|(?:[a-z0-9](?:[-a-z0-9]{0,61}[a-z0-9])?))
Required : Yes
Description : Required. Project ID for this request.
pageToken
Description : Specifies a page token to use. Set `pageToken` to the `nextPageToken` returned by a previous list request to get the next page of results.
Location : query
Type : string
filter
Type : string
Location : query
Description : A filter expression that filters resources listed in the response. Most Compute resources support two types of filter expressions: expressions that support regular expressions and expressions that follow API improvement proposal AIP-160. These two types of filter expressions cannot be mixed in one request. If you want to use AIP-160, your expression must specify the field name, an operator, and the value that you want to use for filtering. The value must be a string, a number, or a boolean. The operator must be either `=`, `!=`, `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute Engine instances, you can exclude instances named `example-instance` by specifying `name != example-instance`. The `:*` comparison can be used to test whether a key has been defined. For example, to find all objects with `owner` label use: ``` labels.owner:* ``` You can also filter nested fields. For example, you could specify `scheduling.automaticRestart = false` to include instances only if they are not scheduled for automatic restarts. You can use filtering on nested fields to filter based onresource labels. To filter on multiple expressions, provide each separate expression within parentheses. For example: ``` (scheduling.automaticRestart = true) (cpuPlatform = "Intel Skylake") ``` By default, each expression is an `AND` expression. However, you can include `AND` and `OR` expressions explicitly. For example: ``` (cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.automaticRestart = true) ``` If you want to use a regular expression, use the `eq` (equal) or `ne` (not equal) operator against a single un-parenthesized expression with or without quotes or against multiple parenthesized expressions. Examples: `fieldname eq unquoted literal` `fieldname eq 'single quoted literal'` `fieldname eq "double quoted literal"` `(fieldname1 eq literal) (fieldname2 ne "literal")` The literal value is interpreted as a regular expression using GoogleRE2 library syntax. The literal value must match the entire field. For example, to filter for instances that do not end with name "instance", you would use `name ne .*instance`. You cannot combine constraints on multiple fields using regular expressions.
maxResults
Default : 500
Minimum : 0
Description : The maximum number of results per page that should be returned. If the number of available results is larger than `maxResults`, Compute Engine returns a `nextPageToken` that can be used to get the next page of results in subsequent list requests. Acceptable values are `0` to `500`, inclusive. (Default: `500`)
Format : uint32
Type : integer
Location : query
orderBy
Description : Sorts list results by a certain order. By default, results are returned in alphanumerical order based on the resource name. You can also sort results in descending order based on the creation timestamp using `orderBy="creationTimestamp desc"`. This sorts results based on the `creationTimestamp` field in reverse chronological order (newest result first). Use this to sort resources like operations so that the newest operation is returned first. Currently, only sorting by `name` or `creationTimestamp desc` is supported.
Type : string
Location : query
Apiversion : 2026-10-01-preview
Parameter Order : project
Description : Lists all VM extensions within a specific zone for a project. This is a read-only API.
▼ ▲ compute.organizationZoneVmExtensionPolicies.delete
Description : Deletes a specified zone VM extension policy within an organization.
Flat Path : organizations/{organizationsId}/zones/{zone}/vmExtensionPolicies/{vmExtensionPolicy}
Path : {+organization}/zones/{zone}/vmExtensionPolicies/{vmExtensionPolicy}
HTTP Method : DELETE
Apiversion : 2026-10-01-preview
Parameters :
zone
Required : Yes
Type : string
Location : path
Description : Name of the zone for this request.
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
organization
Required : Yes
Type : string
Pattern : organizations/[0-9]{0,20}
Description : Organization ID for this request.
Location : path
requestId
Type : string
Description : An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments. The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000).
Location : query
vmExtensionPolicy
Required : Yes
Description : Name of the zone VM extension policy to delete.
Location : path
Type : string
Scopes :
Parameter Order :
▼ ▲ compute.organizationZoneVmExtensionPolicies.listVmExtensions
HTTP Method : GET
Description : Lists all VM extensions within a specific zone for an organization. This is a read-only API.
Apiversion : 2026-10-01-preview
Parameters :
orderBy
Type : string
Description : Sorts list results by a certain order. By default, results are returned in alphanumerical order based on the resource name. You can also sort results in descending order based on the creation timestamp using `orderBy="creationTimestamp desc"`. This sorts results based on the `creationTimestamp` field in reverse chronological order (newest result first). Use this to sort resources like operations so that the newest operation is returned first. Currently, only sorting by `name` or `creationTimestamp desc` is supported.
Location : query
pageToken
Type : string
Description : Specifies a page token to use. Set `pageToken` to the `nextPageToken` returned by a previous list request to get the next page of results.
Location : query
zone
Location : path
Required : Yes
Type : string
Description : Name of the zone for this request.
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
organization
Description : Organization ID for this request.
Required : Yes
Location : path
Type : string
Pattern : organizations/[0-9]{0,20}
maxResults
Format : uint32
Description : The maximum number of results per page that should be returned. If the number of available results is larger than `maxResults`, Compute Engine returns a `nextPageToken` that can be used to get the next page of results in subsequent list requests. Acceptable values are `0` to `500`, inclusive. (Default: `500`)
Type : integer
Location : query
Minimum : 0
Default : 500
filter
Location : query
Description : A filter expression that filters resources listed in the response. Most Compute resources support two types of filter expressions: expressions that support regular expressions and expressions that follow API improvement proposal AIP-160. These two types of filter expressions cannot be mixed in one request. If you want to use AIP-160, your expression must specify the field name, an operator, and the value that you want to use for filtering. The value must be a string, a number, or a boolean. The operator must be either `=`, `!=`, `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute Engine instances, you can exclude instances named `example-instance` by specifying `name != example-instance`. The `:*` comparison can be used to test whether a key has been defined. For example, to find all objects with `owner` label use: ``` labels.owner:* ``` You can also filter nested fields. For example, you could specify `scheduling.automaticRestart = false` to include instances only if they are not scheduled for automatic restarts. You can use filtering on nested fields to filter based onresource labels. To filter on multiple expressions, provide each separate expression within parentheses. For example: ``` (scheduling.automaticRestart = true) (cpuPlatform = "Intel Skylake") ``` By default, each expression is an `AND` expression. However, you can include `AND` and `OR` expressions explicitly. For example: ``` (cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.automaticRestart = true) ``` If you want to use a regular expression, use the `eq` (equal) or `ne` (not equal) operator against a single un-parenthesized expression with or without quotes or against multiple parenthesized expressions. Examples: `fieldname eq unquoted literal` `fieldname eq 'single quoted literal'` `fieldname eq "double quoted literal"` `(fieldname1 eq literal) (fieldname2 ne "literal")` The literal value is interpreted as a regular expression using GoogleRE2 library syntax. The literal value must match the entire field. For example, to filter for instances that do not end with name "instance", you would use `name ne .*instance`. You cannot combine constraints on multiple fields using regular expressions.
Type : string
Parameter Order :
Flat Path : organizations/{organizationsId}/zones/{zone}/vmExtensions
Scopes :
Path : {+organization}/zones/{zone}/vmExtensions
▼ ▲ compute.organizationZoneVmExtensionPolicies.list
HTTP Method : GET
Scopes :
Parameters :
maxResults
Description : The maximum number of results per page that should be returned. If the number of available results is larger than `maxResults`, Compute Engine returns a `nextPageToken` that can be used to get the next page of results in subsequent list requests. Acceptable values are `0` to `500`, inclusive. (Default: `500`)
Location : query
Default : 500
Minimum : 0
Type : integer
Format : uint32
pageToken
Location : query
Type : string
Description : Specifies a page token to use. Set `pageToken` to the `nextPageToken` returned by a previous list request to get the next page of results.
orderBy
Location : query
Type : string
Description : Sorts list results by a certain order. By default, results are returned in alphanumerical order based on the resource name. You can also sort results in descending order based on the creation timestamp using `orderBy="creationTimestamp desc"`. This sorts results based on the `creationTimestamp` field in reverse chronological order (newest result first). Use this to sort resources like operations so that the newest operation is returned first. Currently, only sorting by `name` or `creationTimestamp desc` is supported.
filter
Description : A filter expression that filters resources listed in the response. Most Compute resources support two types of filter expressions: expressions that support regular expressions and expressions that follow API improvement proposal AIP-160. These two types of filter expressions cannot be mixed in one request. If you want to use AIP-160, your expression must specify the field name, an operator, and the value that you want to use for filtering. The value must be a string, a number, or a boolean. The operator must be either `=`, `!=`, `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute Engine instances, you can exclude instances named `example-instance` by specifying `name != example-instance`. The `:*` comparison can be used to test whether a key has been defined. For example, to find all objects with `owner` label use: ``` labels.owner:* ``` You can also filter nested fields. For example, you could specify `scheduling.automaticRestart = false` to include instances only if they are not scheduled for automatic restarts. You can use filtering on nested fields to filter based onresource labels. To filter on multiple expressions, provide each separate expression within parentheses. For example: ``` (scheduling.automaticRestart = true) (cpuPlatform = "Intel Skylake") ``` By default, each expression is an `AND` expression. However, you can include `AND` and `OR` expressions explicitly. For example: ``` (cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.automaticRestart = true) ``` If you want to use a regular expression, use the `eq` (equal) or `ne` (not equal) operator against a single un-parenthesized expression with or without quotes or against multiple parenthesized expressions. Examples: `fieldname eq unquoted literal` `fieldname eq 'single quoted literal'` `fieldname eq "double quoted literal"` `(fieldname1 eq literal) (fieldname2 ne "literal")` The literal value is interpreted as a regular expression using GoogleRE2 library syntax. The literal value must match the entire field. For example, to filter for instances that do not end with name "instance", you would use `name ne .*instance`. You cannot combine constraints on multiple fields using regular expressions.
Location : query
Type : string
organization
Location : path
Pattern : organizations/[0-9]{0,20}
Required : Yes
Description : Organization ID for this request.
Type : string
zone
Type : string
Description : Name of the zone for this request.
Required : Yes
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
Location : path
Apiversion : 2026-10-01-preview
Flat Path : organizations/{organizationsId}/zones/{zone}/vmExtensionPolicies
Parameter Order :
Description : Lists all VM extension policies within a specific zone for an organization.
Path : {+organization}/zones/{zone}/vmExtensionPolicies
▼ ▲ compute.organizationZoneVmExtensionPolicies.update
Scopes :
Parameter Order :
Description : Modifies an existing zone VM extension policy within an organization.
Flat Path : organizations/{organizationsId}/zones/{zone}/vmExtensionPolicies/{vmExtensionPolicy}
HTTP Method : PATCH
Path : {+organization}/zones/{zone}/vmExtensionPolicies/{vmExtensionPolicy}
Apiversion : 2026-10-01-preview
Parameters :
vmExtensionPolicy
Location : path
Type : string
Description : Name of the zone VM extension policy to update.
Required : Yes
requestId
Type : string
Location : query
Description : An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments. The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000).
organization
Required : Yes
Location : path
Type : string
Description : Organization ID for this request.
Pattern : organizations/[0-9]{0,20}
zone
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
Type : string
Location : path
Required : Yes
Description : Name of the zone for this request.
▼ ▲ compute.organizationZoneVmExtensionPolicies.get
Parameters :
organization
Pattern : organizations/[0-9]{0,20}
Required : Yes
Type : string
Location : path
Description : Organization ID for this request.
zone
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
Description : Name of the zone for this request.
Location : path
Type : string
Required : Yes
vmExtensionPolicy
Location : path
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?|[1-9][0-9]{0,19}
Required : Yes
Description : Name of the VM extension policy resource to return.
Type : string
Scopes :
Apiversion : 2026-10-01-preview
Flat Path : organizations/{organizationsId}/zones/{zone}/vmExtensionPolicies/{vmExtensionPolicy}
Description : Retrieves details of a specific zone VM extension policy within an organization.
HTTP Method : GET
Parameter Order :
Path : {+organization}/zones/{zone}/vmExtensionPolicies/{vmExtensionPolicy}
▼ ▲ compute.organizationZoneVmExtensionPolicies.getVmExtension
Scopes :
Flat Path : organizations/{organizationsId}/zones/{zone}/vmExtensions/{extensionName}
Parameters :
extensionName
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?|[1-9][0-9]{0,19}
Type : string
Location : path
Required : Yes
Description : Required. Name of the VM extension for this request.
organization
Pattern : organizations/[0-9]{0,20}
Location : path
Required : Yes
Type : string
Description : Organization ID for this request.
zone
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
Description : Name of the zone for this request.
Required : Yes
Location : path
Type : string
Parameter Order :
Apiversion : 2026-10-01-preview
HTTP Method : GET
Description : Retrieves details of a specific VM extension within an organization.
Path : {+organization}/zones/{zone}/vmExtensions/{extensionName}
▼ ▲ compute.organizationZoneVmExtensionPolicies.insert
Description : Creates a new zone-level VM extension policy within an organization.
Flat Path : organizations/{organizationsId}/zones/{zone}/vmExtensionPolicies
Apiversion : 2026-10-01-preview
Parameters :
organization
Type : string
Pattern : organizations/[0-9]{0,20}
Required : Yes
Location : path
Description : Organization ID for this request.
zone
Type : string
Description : Name of the zone for this request.
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
Location : path
Required : Yes
requestId
Description : An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments. The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000).
Type : string
Location : query
Path : {+organization}/zones/{zone}/vmExtensionPolicies
Scopes :
Parameter Order :
HTTP Method : POST
▼ ▲ compute.zoneOrganizationOperations.list
Flat Path : organizations/{organizationsId}/zones/{zone}/operations
Path : {+organization}/zones/{zone}/operations
Scopes :
Description : Retrieves a list of Operation resources contained within the specified organization.
Parameters :
pageToken
Type : string
Description : Specifies a page token to use. Set `pageToken` to the `nextPageToken` returned by a previous list request to get the next page of results.
Location : query
filter
Type : string
Description : A filter expression that filters resources listed in the response. Most Compute resources support two types of filter expressions: expressions that support regular expressions and expressions that follow API improvement proposal AIP-160. These two types of filter expressions cannot be mixed in one request. If you want to use AIP-160, your expression must specify the field name, an operator, and the value that you want to use for filtering. The value must be a string, a number, or a boolean. The operator must be either `=`, `!=`, `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute Engine instances, you can exclude instances named `example-instance` by specifying `name != example-instance`. The `:*` comparison can be used to test whether a key has been defined. For example, to find all objects with `owner` label use: ``` labels.owner:* ``` You can also filter nested fields. For example, you could specify `scheduling.automaticRestart = false` to include instances only if they are not scheduled for automatic restarts. You can use filtering on nested fields to filter based onresource labels. To filter on multiple expressions, provide each separate expression within parentheses. For example: ``` (scheduling.automaticRestart = true) (cpuPlatform = "Intel Skylake") ``` By default, each expression is an `AND` expression. However, you can include `AND` and `OR` expressions explicitly. For example: ``` (cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.automaticRestart = true) ``` If you want to use a regular expression, use the `eq` (equal) or `ne` (not equal) operator against a single un-parenthesized expression with or without quotes or against multiple parenthesized expressions. Examples: `fieldname eq unquoted literal` `fieldname eq 'single quoted literal'` `fieldname eq "double quoted literal"` `(fieldname1 eq literal) (fieldname2 ne "literal")` The literal value is interpreted as a regular expression using GoogleRE2 library syntax. The literal value must match the entire field. For example, to filter for instances that do not end with name "instance", you would use `name ne .*instance`. You cannot combine constraints on multiple fields using regular expressions.
Location : query
zone
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
Location : path
Required : Yes
Type : string
Description : Name of the zone for request.
maxResults
Default : 500
Minimum : 0
Location : query
Description : The maximum number of results per page that should be returned. If the number of available results is larger than `maxResults`, Compute Engine returns a `nextPageToken` that can be used to get the next page of results in subsequent list requests. Acceptable values are `0` to `500`, inclusive. (Default: `500`)
Type : integer
Format : uint32
organization
Required : Yes
Location : path
Type : string
Description : Organization ID for this request.
Pattern : ^organizations/[^/]+$
orderBy
Description : Sorts list results by a certain order. By default, results are returned in alphanumerical order based on the resource name. You can also sort results in descending order based on the creation timestamp using `orderBy="creationTimestamp desc"`. This sorts results based on the `creationTimestamp` field in reverse chronological order (newest result first). Use this to sort resources like operations so that the newest operation is returned first. Currently, only sorting by `name` or `creationTimestamp desc` is supported.
Type : string
Location : query
Apiversion : 2026-10-01-preview
Parameter Order :
HTTP Method : GET
▼ ▲ compute.zoneOrganizationOperations.get
Parameter Order :
Description : Retrieves the specified Operations resource.
Flat Path : organizations/{organizationsId}/zones/{zone}/operations/{operation}
Apiversion : 2026-10-01-preview
Path : {+organization}/zones/{zone}/operations/{operation}
Parameters :
organization
Description : Organization ID for this request.
Type : string
Required : Yes
Pattern : organizations/[0-9]{0,20}
Location : path
zone
Required : Yes
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
Location : path
Description : Name of the zone for this request.
Type : string
operation
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?|[1-9][0-9]{0,19}
Location : path
Required : Yes
Type : string
Description : Name of the Operations resource to return. Parent is derived from this field.
Scopes :
HTTP Method : GET
▼ ▲ compute.sslCertificates.fetchEncryptionKey
Description : Returns the public encryption key used to encrypt the TLS private key before upload.
Parameters :
project
Location : path
Required : Yes
Pattern : (?:(?:[-a-z0-9]{1,63}\.)*(?:[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?):)?(?:[0-9]{1,19}|(?:[a-z0-9](?:[-a-z0-9]{0,61}[a-z0-9])?))
Description : Project ID for this request.
Type : string
Scopes :
Apiversion : 2026-10-01-preview
HTTP Method : GET
Path : projects/{project}/global/sslCertificates/encryptionKey
Flat Path : projects/{project}/global/sslCertificates/encryptionKey
Parameter Order : project
▼ ▲ compute.instances.update
Parameters :
minimalAction
Enum Descriptions The instance will restart on the same host. Data on all local SSDs will be preserved.
Enum RESTART_IN_PLACE
mostDisruptiveAllowedAction
Enum RESTART_IN_PLACE
Enum Descriptions The instance will restart on the same host. Data on all local SSDs will be preserved.
▼ ▲ compute.instances.troubleshoot
HTTP Method : POST
Parameter Order :
Apiversion : 2026-10-01-preview
Parameters :
requestId
Location : query
Type : string
Description : An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments. The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000).
params.endTime
Description : Input only. Timestamp representing the end of the troubleshooting window in RFC3339 text format. If omitted, defaults to 'now'.
Location : query
Type : string
project
Location : path
Description : Project ID for this request.
Required : Yes
Pattern : (?:(?:[-a-z0-9]{1,63}\.)*(?:[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?):)?(?:[0-9]{1,19}|(?:[a-z0-9](?:[-a-z0-9]{0,61}[a-z0-9])?))
Type : string
instance
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?|[1-9][0-9]{0,19}
Required : Yes
Type : string
Description : Name of the instance scoping this request.
Location : path
params.startTime
Description : Input only. Timestamp representing the beginning of the troubleshooting window in RFC3339 text format. If omitted, defaults to the last 12 hours.
Location : query
Type : string
zone
Location : path
Description : The name of the zone for this request.
Required : Yes
Type : string
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
Description : Initiates diagnostic troubleshooting on the specified instance. This operation cannot be cancelled.
Scopes :
Flat Path : projects/{project}/zones/{zone}/instances/{instance}/troubleshoot
Path : projects/{project}/zones/{zone}/instances/{instance}/troubleshoot
▼ ▲ compute.instances.troubleshoot
HTTP Method : POST
Parameter Order :
Apiversion : 2026-10-01-preview
Parameters :
requestId
Location : query
Type : string
Description : An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments. The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000).
params.endTime
Description : Input only. Timestamp representing the end of the troubleshooting window in RFC3339 text format. If omitted, defaults to 'now'.
Location : query
Type : string
project
Location : path
Description : Project ID for this request.
Required : Yes
Pattern : (?:(?:[-a-z0-9]{1,63}\.)*(?:[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?):)?(?:[0-9]{1,19}|(?:[a-z0-9](?:[-a-z0-9]{0,61}[a-z0-9])?))
Type : string
instance
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?|[1-9][0-9]{0,19}
Required : Yes
Type : string
Description : Name of the instance scoping this request.
Location : path
params.startTime
Description : Input only. Timestamp representing the beginning of the troubleshooting window in RFC3339 text format. If omitted, defaults to the last 12 hours.
Location : query
Type : string
zone
Location : path
Description : The name of the zone for this request.
Required : Yes
Type : string
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
Description : Initiates diagnostic troubleshooting on the specified instance. This operation cannot be cancelled.
Scopes :
Flat Path : projects/{project}/zones/{zone}/instances/{instance}/troubleshoot
Path : projects/{project}/zones/{zone}/instances/{instance}/troubleshoot
▼ ▲ compute.instances.update
Parameters :
minimalAction
Enum Descriptions The instance will restart on the same host. Data on all local SSDs will be preserved.
Enum RESTART_IN_PLACE
mostDisruptiveAllowedAction
Enum Descriptions The instance will restart on the same host. Data on all local SSDs will be preserved.
Enum RESTART_IN_PLACE
▼ ▲ compute.zoneOrganizationOperations.list
Path : {+organization}/zones/{zone}/operations
Flat Path : organizations/{organizationsId}/zones/{zone}/operations
Parameter Order :
HTTP Method : GET
Parameters :
filter
Location : query
Description : A filter expression that filters resources listed in the response. Most Compute resources support two types of filter expressions: expressions that support regular expressions and expressions that follow API improvement proposal AIP-160. These two types of filter expressions cannot be mixed in one request. If you want to use AIP-160, your expression must specify the field name, an operator, and the value that you want to use for filtering. The value must be a string, a number, or a boolean. The operator must be either `=`, `!=`, `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute Engine instances, you can exclude instances named `example-instance` by specifying `name != example-instance`. The `:*` comparison can be used to test whether a key has been defined. For example, to find all objects with `owner` label use: ``` labels.owner:* ``` You can also filter nested fields. For example, you could specify `scheduling.automaticRestart = false` to include instances only if they are not scheduled for automatic restarts. You can use filtering on nested fields to filter based onresource labels. To filter on multiple expressions, provide each separate expression within parentheses. For example: ``` (scheduling.automaticRestart = true) (cpuPlatform = "Intel Skylake") ``` By default, each expression is an `AND` expression. However, you can include `AND` and `OR` expressions explicitly. For example: ``` (cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.automaticRestart = true) ``` If you want to use a regular expression, use the `eq` (equal) or `ne` (not equal) operator against a single un-parenthesized expression with or without quotes or against multiple parenthesized expressions. Examples: `fieldname eq unquoted literal` `fieldname eq 'single quoted literal'` `fieldname eq "double quoted literal"` `(fieldname1 eq literal) (fieldname2 ne "literal")` The literal value is interpreted as a regular expression using GoogleRE2 library syntax. The literal value must match the entire field. For example, to filter for instances that do not end with name "instance", you would use `name ne .*instance`. You cannot combine constraints on multiple fields using regular expressions.
Type : string
zone
Description : Name of the zone for request.
Type : string
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
Location : path
Required : Yes
maxResults
Minimum : 0
Format : uint32
Type : integer
Default : 500
Location : query
Description : The maximum number of results per page that should be returned. If the number of available results is larger than `maxResults`, Compute Engine returns a `nextPageToken` that can be used to get the next page of results in subsequent list requests. Acceptable values are `0` to `500`, inclusive. (Default: `500`)
orderBy
Location : query
Description : Sorts list results by a certain order. By default, results are returned in alphanumerical order based on the resource name. You can also sort results in descending order based on the creation timestamp using `orderBy="creationTimestamp desc"`. This sorts results based on the `creationTimestamp` field in reverse chronological order (newest result first). Use this to sort resources like operations so that the newest operation is returned first. Currently, only sorting by `name` or `creationTimestamp desc` is supported.
Type : string
pageToken
Type : string
Description : Specifies a page token to use. Set `pageToken` to the `nextPageToken` returned by a previous list request to get the next page of results.
Location : query
organization
Type : string
Description : Organization ID for this request.
Pattern : ^organizations/[^/]+$
Location : path
Required : Yes
Scopes :
Apiversion : 2026-10-01-preview
Description : Retrieves a list of Operation resources contained within the specified organization.
▼ ▲ compute.zoneOrganizationOperations.get
Description : Retrieves the specified Operations resource.
Apiversion : 2026-10-01-preview
Parameter Order :
HTTP Method : GET
Parameters :
zone
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
Type : string
Description : Name of the zone for this request.
Location : path
Required : Yes
operation
Description : Name of the Operations resource to return. Parent is derived from this field.
Type : string
Location : path
Required : Yes
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?|[1-9][0-9]{0,19}
organization
Type : string
Pattern : organizations/[0-9]{0,20}
Location : path
Required : Yes
Description : Organization ID for this request.
Path : {+organization}/zones/{zone}/operations/{operation}
Scopes :
Flat Path : organizations/{organizationsId}/zones/{zone}/operations/{operation}
▼ ▲ compute.globalVmExtensionPolicies.listVmExtensions
Description : Lists all VM extensions within a specific zone for a project. This is a read-only API.
Parameter Order : project
HTTP Method : GET
Parameters :
project
Description : Required. Project ID for this request.
Type : string
Location : path
Required : Yes
Pattern : (?:(?:[-a-z0-9]{1,63}\.)*(?:[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?):)?(?:[0-9]{1,19}|(?:[a-z0-9](?:[-a-z0-9]{0,61}[a-z0-9])?))
pageToken
Description : Specifies a page token to use. Set `pageToken` to the `nextPageToken` returned by a previous list request to get the next page of results.
Location : query
Type : string
filter
Type : string
Location : query
Description : A filter expression that filters resources listed in the response. Most Compute resources support two types of filter expressions: expressions that support regular expressions and expressions that follow API improvement proposal AIP-160. These two types of filter expressions cannot be mixed in one request. If you want to use AIP-160, your expression must specify the field name, an operator, and the value that you want to use for filtering. The value must be a string, a number, or a boolean. The operator must be either `=`, `!=`, `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute Engine instances, you can exclude instances named `example-instance` by specifying `name != example-instance`. The `:*` comparison can be used to test whether a key has been defined. For example, to find all objects with `owner` label use: ``` labels.owner:* ``` You can also filter nested fields. For example, you could specify `scheduling.automaticRestart = false` to include instances only if they are not scheduled for automatic restarts. You can use filtering on nested fields to filter based onresource labels. To filter on multiple expressions, provide each separate expression within parentheses. For example: ``` (scheduling.automaticRestart = true) (cpuPlatform = "Intel Skylake") ``` By default, each expression is an `AND` expression. However, you can include `AND` and `OR` expressions explicitly. For example: ``` (cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.automaticRestart = true) ``` If you want to use a regular expression, use the `eq` (equal) or `ne` (not equal) operator against a single un-parenthesized expression with or without quotes or against multiple parenthesized expressions. Examples: `fieldname eq unquoted literal` `fieldname eq 'single quoted literal'` `fieldname eq "double quoted literal"` `(fieldname1 eq literal) (fieldname2 ne "literal")` The literal value is interpreted as a regular expression using GoogleRE2 library syntax. The literal value must match the entire field. For example, to filter for instances that do not end with name "instance", you would use `name ne .*instance`. You cannot combine constraints on multiple fields using regular expressions.
maxResults
Format : uint32
Type : integer
Description : The maximum number of results per page that should be returned. If the number of available results is larger than `maxResults`, Compute Engine returns a `nextPageToken` that can be used to get the next page of results in subsequent list requests. Acceptable values are `0` to `500`, inclusive. (Default: `500`)
Minimum : 0
Location : query
Default : 500
orderBy
Location : query
Description : Sorts list results by a certain order. By default, results are returned in alphanumerical order based on the resource name. You can also sort results in descending order based on the creation timestamp using `orderBy="creationTimestamp desc"`. This sorts results based on the `creationTimestamp` field in reverse chronological order (newest result first). Use this to sort resources like operations so that the newest operation is returned first. Currently, only sorting by `name` or `creationTimestamp desc` is supported.
Type : string
Flat Path : projects/{project}/global/vmExtensions
Scopes :
Apiversion : 2026-10-01-preview
Path : projects/{project}/global/vmExtensions
▼ ▲ compute.globalVmExtensionPolicies.getVmExtension
Path : projects/{project}/global/vmExtensions/{extensionName}
Description : Retrieves details of a specific VM extension.
Apiversion : 2026-10-01-preview
Scopes :
HTTP Method : GET
Parameters :
project
Type : string
Pattern : (?:(?:[-a-z0-9]{1,63}\.)*(?:[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?):)?(?:[0-9]{1,19}|(?:[a-z0-9](?:[-a-z0-9]{0,61}[a-z0-9])?))
Location : path
Required : Yes
Description : Project ID for this request.
extensionName
Location : path
Required : Yes
Type : string
Description : Required. Name of the VM extension for this request.
Parameter Order :
Flat Path : projects/{project}/global/vmExtensions/{extensionName}
▼ ▲ compute.organizationGlobalVmExtensionPolicies.aggregatedList
Parameter Order : organization
Path : {+organization}/aggregated/vmExtensionPolicies
Scopes :
Description : Retrieves the list of all organization level VM Extension Policy resources available to the specified organization. To prevent failure, it's recommended that you set the `returnPartialSuccess` parameter to `true`.
HTTP Method : GET
Parameters :
maxResults
Type : integer
Format : uint32
Description : The maximum number of results per page that should be returned. If the number of available results is larger than `maxResults`, Compute Engine returns a `nextPageToken` that can be used to get the next page of results in subsequent list requests. Acceptable values are `0` to `500`, inclusive. (Default: `500`)
Minimum : 0
Location : query
Default : 500
filter
Description : A filter expression that filters resources listed in the response. Most Compute resources support two types of filter expressions: expressions that support regular expressions and expressions that follow API improvement proposal AIP-160. These two types of filter expressions cannot be mixed in one request. If you want to use AIP-160, your expression must specify the field name, an operator, and the value that you want to use for filtering. The value must be a string, a number, or a boolean. The operator must be either `=`, `!=`, `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute Engine instances, you can exclude instances named `example-instance` by specifying `name != example-instance`. The `:*` comparison can be used to test whether a key has been defined. For example, to find all objects with `owner` label use: ``` labels.owner:* ``` You can also filter nested fields. For example, you could specify `scheduling.automaticRestart = false` to include instances only if they are not scheduled for automatic restarts. You can use filtering on nested fields to filter based onresource labels. To filter on multiple expressions, provide each separate expression within parentheses. For example: ``` (scheduling.automaticRestart = true) (cpuPlatform = "Intel Skylake") ``` By default, each expression is an `AND` expression. However, you can include `AND` and `OR` expressions explicitly. For example: ``` (cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.automaticRestart = true) ``` If you want to use a regular expression, use the `eq` (equal) or `ne` (not equal) operator against a single un-parenthesized expression with or without quotes or against multiple parenthesized expressions. Examples: `fieldname eq unquoted literal` `fieldname eq 'single quoted literal'` `fieldname eq "double quoted literal"` `(fieldname1 eq literal) (fieldname2 ne "literal")` The literal value is interpreted as a regular expression using GoogleRE2 library syntax. The literal value must match the entire field. For example, to filter for instances that do not end with name "instance", you would use `name ne .*instance`. You cannot combine constraints on multiple fields using regular expressions.
Type : string
Location : query
pageToken
Description : Specifies a page token to use. Set `pageToken` to the `nextPageToken` returned by a previous list request to get the next page of results.
Type : string
Location : query
serviceProjectNumber
Location : query
Type : string
Description : The Shared VPC service project id or service project number for which aggregated list request is invoked for subnetworks list-usable api.
Format : int64
orderBy
Description : Sorts list results by a certain order. By default, results are returned in alphanumerical order based on the resource name. You can also sort results in descending order based on the creation timestamp using `orderBy="creationTimestamp desc"`. This sorts results based on the `creationTimestamp` field in reverse chronological order (newest result first). Use this to sort resources like operations so that the newest operation is returned first. Currently, only sorting by `name` or `creationTimestamp desc` is supported.
Location : query
Type : string
organization
Location : path
Required : Yes
Description : Organization ID for this request.
Type : string
Pattern : organizations/[0-9]{0,20}
includeAllScopes
Type : boolean
Description : Indicates whether every visible scope for each scope type (zone, region, global) should be included in the response. For new resource types added after this field, the flag has no effect as new resource types will always include every visible scope for each scope type in response. For resource types which predate this field, if this flag is omitted or false, only scopes of the scope types where the resource type is expected to be found will be included.
Location : query
Flat Path : organizations/{organizationsId}/aggregated/vmExtensionPolicies
Apiversion : 2026-10-01-preview
▼ ▲ compute.organizationGlobalVmExtensionPolicies.get
Scopes :
Parameter Order :
Flat Path : organizations/{organizationsId}/global/vmExtensionPolicies/{globalVmExtensionPolicy}
Description : Gets details of an organization level GlobalVmExtensionPolicy.
Path : {+organization}/global/vmExtensionPolicies/{globalVmExtensionPolicy}
HTTP Method : GET
Parameters :
globalVmExtensionPolicy
Description : Name of the GlobalVmExtensionPolicy resource to return.
Location : path
Required : Yes
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?|[1-9][0-9]{0,19}
Type : string
organization
Type : string
Pattern : organizations/[0-9]{0,20}
Location : path
Required : Yes
Description : Organization ID for this request.
Apiversion : 2026-10-01-preview
▼ ▲ compute.organizationGlobalVmExtensionPolicies.delete
Path : {+organization}/global/vmExtensionPolicies/{globalVmExtensionPolicy}/delete
Parameter Order :
Scopes :
Description : Purge scoped resources (zonal policies) from an organization level global VM extension policy, and then delete the global VM extension policy. Purge of the scoped resources is a pre-condition of the global VM extension policy deletion. The deletion of the global VM extension policy happens after the purge rollout is done, so it's not a part of the LRO. It's an automatic process that triggers in the backend.
Apiversion : 2026-10-01-preview
Flat Path : organizations/{organizationsId}/global/vmExtensionPolicies/{globalVmExtensionPolicy}/delete
HTTP Method : POST
Parameters :
globalVmExtensionPolicy
Location : path
Required : Yes
Description : Name of the global VM extension policy to purge scoped resources for.
Type : string
requestId
Location : query
Type : string
Description : An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments. The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000).
organization
Pattern : organizations/[0-9]{0,20}
Location : path
Required : Yes
Type : string
Description : Organization ID for this request.
▼ ▲ compute.organizationGlobalVmExtensionPolicies.listVmExtensions
Path : {+organization}/global/vmExtensions
Flat Path : organizations/{organizationsId}/global/vmExtensions
Apiversion : 2026-10-01-preview
Scopes :
HTTP Method : GET
Parameters :
maxResults
Default : 500
Location : query
Description : The maximum number of results per page that should be returned. If the number of available results is larger than `maxResults`, Compute Engine returns a `nextPageToken` that can be used to get the next page of results in subsequent list requests. Acceptable values are `0` to `500`, inclusive. (Default: `500`)
Minimum : 0
Type : integer
Format : uint32
orderBy
Type : string
Description : Sorts list results by a certain order. By default, results are returned in alphanumerical order based on the resource name. You can also sort results in descending order based on the creation timestamp using `orderBy="creationTimestamp desc"`. This sorts results based on the `creationTimestamp` field in reverse chronological order (newest result first). Use this to sort resources like operations so that the newest operation is returned first. Currently, only sorting by `name` or `creationTimestamp desc` is supported.
Location : query
filter
Location : query
Description : A filter expression that filters resources listed in the response. Most Compute resources support two types of filter expressions: expressions that support regular expressions and expressions that follow API improvement proposal AIP-160. These two types of filter expressions cannot be mixed in one request. If you want to use AIP-160, your expression must specify the field name, an operator, and the value that you want to use for filtering. The value must be a string, a number, or a boolean. The operator must be either `=`, `!=`, `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute Engine instances, you can exclude instances named `example-instance` by specifying `name != example-instance`. The `:*` comparison can be used to test whether a key has been defined. For example, to find all objects with `owner` label use: ``` labels.owner:* ``` You can also filter nested fields. For example, you could specify `scheduling.automaticRestart = false` to include instances only if they are not scheduled for automatic restarts. You can use filtering on nested fields to filter based onresource labels. To filter on multiple expressions, provide each separate expression within parentheses. For example: ``` (scheduling.automaticRestart = true) (cpuPlatform = "Intel Skylake") ``` By default, each expression is an `AND` expression. However, you can include `AND` and `OR` expressions explicitly. For example: ``` (cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.automaticRestart = true) ``` If you want to use a regular expression, use the `eq` (equal) or `ne` (not equal) operator against a single un-parenthesized expression with or without quotes or against multiple parenthesized expressions. Examples: `fieldname eq unquoted literal` `fieldname eq 'single quoted literal'` `fieldname eq "double quoted literal"` `(fieldname1 eq literal) (fieldname2 ne "literal")` The literal value is interpreted as a regular expression using GoogleRE2 library syntax. The literal value must match the entire field. For example, to filter for instances that do not end with name "instance", you would use `name ne .*instance`. You cannot combine constraints on multiple fields using regular expressions.
Type : string
organization
Location : path
Required : Yes
Description : Required. Organization ID for this request.
Type : string
Pattern : organizations/[0-9]{0,20}
pageToken
Type : string
Location : query
Description : Specifies a page token to use. Set `pageToken` to the `nextPageToken` returned by a previous list request to get the next page of results.
Description : Lists all VM extensions within an organization. This is a read-only API.
Parameter Order : organization
▼ ▲ compute.organizationGlobalVmExtensionPolicies.getVmExtension
Scopes :
Parameter Order :
Flat Path : organizations/{organizationsId}/global/vmExtensions/{extensionName}
Path : {+organization}/global/vmExtensions/{extensionName}
Apiversion : 2026-10-01-preview
Description : Retrieves details of a specific VM extension.
HTTP Method : GET
Parameters :
extensionName
Location : path
Required : Yes
Type : string
Description : Required. Name of the VM extension for this request.
organization
Type : string
Location : path
Required : Yes
Description : Organization ID for this request.
Pattern : organizations/[0-9]{0,20}
▼ ▲ compute.organizationGlobalVmExtensionPolicies.list
Scopes :
Parameter Order : organization
Description : Lists organization level GlobalVmExtensionPolicies.
Path : {+organization}/global/vmExtensionPolicies
Flat Path : organizations/{organizationsId}/global/vmExtensionPolicies
HTTP Method : GET
Parameters :
organization
Location : path
Required : Yes
Pattern : organizations/[0-9]{0,20}
Type : string
Description : Organization ID for this request.
filter
Description : A filter expression that filters resources listed in the response. Most Compute resources support two types of filter expressions: expressions that support regular expressions and expressions that follow API improvement proposal AIP-160. These two types of filter expressions cannot be mixed in one request. If you want to use AIP-160, your expression must specify the field name, an operator, and the value that you want to use for filtering. The value must be a string, a number, or a boolean. The operator must be either `=`, `!=`, `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute Engine instances, you can exclude instances named `example-instance` by specifying `name != example-instance`. The `:*` comparison can be used to test whether a key has been defined. For example, to find all objects with `owner` label use: ``` labels.owner:* ``` You can also filter nested fields. For example, you could specify `scheduling.automaticRestart = false` to include instances only if they are not scheduled for automatic restarts. You can use filtering on nested fields to filter based onresource labels. To filter on multiple expressions, provide each separate expression within parentheses. For example: ``` (scheduling.automaticRestart = true) (cpuPlatform = "Intel Skylake") ``` By default, each expression is an `AND` expression. However, you can include `AND` and `OR` expressions explicitly. For example: ``` (cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.automaticRestart = true) ``` If you want to use a regular expression, use the `eq` (equal) or `ne` (not equal) operator against a single un-parenthesized expression with or without quotes or against multiple parenthesized expressions. Examples: `fieldname eq unquoted literal` `fieldname eq 'single quoted literal'` `fieldname eq "double quoted literal"` `(fieldname1 eq literal) (fieldname2 ne "literal")` The literal value is interpreted as a regular expression using GoogleRE2 library syntax. The literal value must match the entire field. For example, to filter for instances that do not end with name "instance", you would use `name ne .*instance`. You cannot combine constraints on multiple fields using regular expressions.
Type : string
Location : query
pageToken
Description : Specifies a page token to use. Set `pageToken` to the `nextPageToken` returned by a previous list request to get the next page of results.
Type : string
Location : query
orderBy
Location : query
Description : Sorts list results by a certain order. By default, results are returned in alphanumerical order based on the resource name. You can also sort results in descending order based on the creation timestamp using `orderBy="creationTimestamp desc"`. This sorts results based on the `creationTimestamp` field in reverse chronological order (newest result first). Use this to sort resources like operations so that the newest operation is returned first. Currently, only sorting by `name` or `creationTimestamp desc` is supported.
Type : string
maxResults
Description : The maximum number of results per page that should be returned. If the number of available results is larger than `maxResults`, Compute Engine returns a `nextPageToken` that can be used to get the next page of results in subsequent list requests. Acceptable values are `0` to `500`, inclusive. (Default: `500`)
Format : uint32
Location : query
Minimum : 0
Type : integer
Default : 500
Apiversion : 2026-10-01-preview
▼ ▲ compute.organizationGlobalVmExtensionPolicies.insert
Scopes :
Parameter Order : organization
Flat Path : organizations/{organizationsId}/global/vmExtensionPolicies
Description : Creates a new organization level GlobalVmExtensionPolicy.
HTTP Method : POST
Parameters :
organization
Description : Organization ID for this request.
Location : path
Required : Yes
Type : string
Pattern : organizations/[0-9]{0,20}
requestId
Type : string
Location : query
Description : An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments. The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000).
Path : {+organization}/global/vmExtensionPolicies
Apiversion : 2026-10-01-preview
▼ ▲ compute.organizationGlobalVmExtensionPolicies.update
Flat Path : organizations/{organizationsId}/global/vmExtensionPolicies/{globalVmExtensionPolicy}
Path : {+organization}/global/vmExtensionPolicies/{globalVmExtensionPolicy}
Scopes :
Description : Updates an organization level GlobalVmExtensionPolicy.
Apiversion : 2026-10-01-preview
Parameter Order :
HTTP Method : PATCH
Parameters :
organization
Type : string
Pattern : organizations/[0-9]{0,20}
Location : path
Required : Yes
Description : Organization ID for this request.
globalVmExtensionPolicy
Location : path
Required : Yes
Type : string
Description : Name of the global VM extension policy to update.
requestId
Description : An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments. The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000).
Location : query
Type : string
▼ ▲ compute.zoneVmExtensionPolicies.listVmExtensions
Apiversion : 2026-10-01-preview
Parameter Order :
Description : Lists all VM extensions within a specific zone for a project. This is a read-only API.
HTTP Method : GET
Parameters :
maxResults
Location : query
Minimum : 0
Default : 500
Description : The maximum number of results per page that should be returned. If the number of available results is larger than `maxResults`, Compute Engine returns a `nextPageToken` that can be used to get the next page of results in subsequent list requests. Acceptable values are `0` to `500`, inclusive. (Default: `500`)
Type : integer
Format : uint32
project
Type : string
Pattern : (?:(?:[-a-z0-9]{1,63}\.)*(?:[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?):)?(?:[0-9]{1,19}|(?:[a-z0-9](?:[-a-z0-9]{0,61}[a-z0-9])?))
Location : path
Required : Yes
Description : Required. Project ID for this request.
pageToken
Type : string
Description : Specifies a page token to use. Set `pageToken` to the `nextPageToken` returned by a previous list request to get the next page of results.
Location : query
zone
Type : string
Description : Name of the zone for this request.
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
Location : path
Required : Yes
orderBy
Location : query
Description : Sorts list results by a certain order. By default, results are returned in alphanumerical order based on the resource name. You can also sort results in descending order based on the creation timestamp using `orderBy="creationTimestamp desc"`. This sorts results based on the `creationTimestamp` field in reverse chronological order (newest result first). Use this to sort resources like operations so that the newest operation is returned first. Currently, only sorting by `name` or `creationTimestamp desc` is supported.
Type : string
filter
Description : A filter expression that filters resources listed in the response. Most Compute resources support two types of filter expressions: expressions that support regular expressions and expressions that follow API improvement proposal AIP-160. These two types of filter expressions cannot be mixed in one request. If you want to use AIP-160, your expression must specify the field name, an operator, and the value that you want to use for filtering. The value must be a string, a number, or a boolean. The operator must be either `=`, `!=`, `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute Engine instances, you can exclude instances named `example-instance` by specifying `name != example-instance`. The `:*` comparison can be used to test whether a key has been defined. For example, to find all objects with `owner` label use: ``` labels.owner:* ``` You can also filter nested fields. For example, you could specify `scheduling.automaticRestart = false` to include instances only if they are not scheduled for automatic restarts. You can use filtering on nested fields to filter based onresource labels. To filter on multiple expressions, provide each separate expression within parentheses. For example: ``` (scheduling.automaticRestart = true) (cpuPlatform = "Intel Skylake") ``` By default, each expression is an `AND` expression. However, you can include `AND` and `OR` expressions explicitly. For example: ``` (cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.automaticRestart = true) ``` If you want to use a regular expression, use the `eq` (equal) or `ne` (not equal) operator against a single un-parenthesized expression with or without quotes or against multiple parenthesized expressions. Examples: `fieldname eq unquoted literal` `fieldname eq 'single quoted literal'` `fieldname eq "double quoted literal"` `(fieldname1 eq literal) (fieldname2 ne "literal")` The literal value is interpreted as a regular expression using GoogleRE2 library syntax. The literal value must match the entire field. For example, to filter for instances that do not end with name "instance", you would use `name ne .*instance`. You cannot combine constraints on multiple fields using regular expressions.
Location : query
Type : string
Path : projects/{project}/zones/{zone}/vmExtensions
Scopes :
Flat Path : projects/{project}/zones/{zone}/vmExtensions
▼ ▲ compute.zoneVmExtensionPolicies.getVmExtension
HTTP Method : GET
Parameters :
project
Description : Project ID for this request.
Type : string
Pattern : (?:(?:[-a-z0-9]{1,63}\.)*(?:[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?):)?(?:[0-9]{1,19}|(?:[a-z0-9](?:[-a-z0-9]{0,61}[a-z0-9])?))
Location : path
Required : Yes
zone
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
Type : string
Location : path
Required : Yes
Description : Name of the zone for this request.
extensionName
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?|[1-9][0-9]{0,19}
Location : path
Required : Yes
Type : string
Description : Required. Name of the VM extension for this request.
Flat Path : projects/{project}/zones/{zone}/vmExtensions/{extensionName}
Description : Retrieves details of a specific VM extension within a project.
Path : projects/{project}/zones/{zone}/vmExtensions/{extensionName}
Parameter Order :
Apiversion : 2026-10-01-preview
Scopes :
▼ ▲ compute.sslCertificates.fetchEncryptionKey
Path : projects/{project}/global/sslCertificates/encryptionKey
Description : Returns the public encryption key used to encrypt the TLS private key before upload.
HTTP Method : GET
Parameters :
project
Pattern : (?:(?:[-a-z0-9]{1,63}\.)*(?:[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?):)?(?:[0-9]{1,19}|(?:[a-z0-9](?:[-a-z0-9]{0,61}[a-z0-9])?))
Type : string
Location : path
Required : Yes
Description : Project ID for this request.
Scopes :
Parameter Order : project
Apiversion : 2026-10-01-preview
Flat Path : projects/{project}/global/sslCertificates/encryptionKey
▼ ▲ compute.globalFolderOperations.list
Apiversion : 2026-10-01-preview
Path : {+folder}/global/operations
Description : Retrieves a list of Operation resources contained within the specified folder.
HTTP Method : GET
Parameters :
maxResults
Description : The maximum number of results per page that should be returned. If the number of available results is larger than `maxResults`, Compute Engine returns a `nextPageToken` that can be used to get the next page of results in subsequent list requests. Acceptable values are `0` to `500`, inclusive. (Default: `500`)
Minimum : 0
Format : uint32
Default : 500
Location : query
Type : integer
orderBy
Location : query
Description : Sorts list results by a certain order. By default, results are returned in alphanumerical order based on the resource name. You can also sort results in descending order based on the creation timestamp using `orderBy="creationTimestamp desc"`. This sorts results based on the `creationTimestamp` field in reverse chronological order (newest result first). Use this to sort resources like operations so that the newest operation is returned first. Currently, only sorting by `name` or `creationTimestamp desc` is supported.
Type : string
pageToken
Location : query
Description : Specifies a page token to use. Set `pageToken` to the `nextPageToken` returned by a previous list request to get the next page of results.
Type : string
filter
Location : query
Type : string
Description : A filter expression that filters resources listed in the response. Most Compute resources support two types of filter expressions: expressions that support regular expressions and expressions that follow API improvement proposal AIP-160. These two types of filter expressions cannot be mixed in one request. If you want to use AIP-160, your expression must specify the field name, an operator, and the value that you want to use for filtering. The value must be a string, a number, or a boolean. The operator must be either `=`, `!=`, `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute Engine instances, you can exclude instances named `example-instance` by specifying `name != example-instance`. The `:*` comparison can be used to test whether a key has been defined. For example, to find all objects with `owner` label use: ``` labels.owner:* ``` You can also filter nested fields. For example, you could specify `scheduling.automaticRestart = false` to include instances only if they are not scheduled for automatic restarts. You can use filtering on nested fields to filter based onresource labels. To filter on multiple expressions, provide each separate expression within parentheses. For example: ``` (scheduling.automaticRestart = true) (cpuPlatform = "Intel Skylake") ``` By default, each expression is an `AND` expression. However, you can include `AND` and `OR` expressions explicitly. For example: ``` (cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.automaticRestart = true) ``` If you want to use a regular expression, use the `eq` (equal) or `ne` (not equal) operator against a single un-parenthesized expression with or without quotes or against multiple parenthesized expressions. Examples: `fieldname eq unquoted literal` `fieldname eq 'single quoted literal'` `fieldname eq "double quoted literal"` `(fieldname1 eq literal) (fieldname2 ne "literal")` The literal value is interpreted as a regular expression using GoogleRE2 library syntax. The literal value must match the entire field. For example, to filter for instances that do not end with name "instance", you would use `name ne .*instance`. You cannot combine constraints on multiple fields using regular expressions.
folder
Location : path
Required : Yes
Description : Folder ID for this request.
Pattern : folders/[0-9]{0,20}
Type : string
Parameter Order : folder
Scopes :
Flat Path : folders/{foldersId}/global/operations
▼ ▲ compute.globalFolderOperations.get
Parameter Order :
Description : Retrieves the specified Operations resource.
Path : {+folder}/global/operations/{operation}
Flat Path : folders/{foldersId}/global/operations/{operation}
Apiversion : 2026-10-01-preview
HTTP Method : GET
Parameters :
operation
Location : path
Required : Yes
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?|[1-9][0-9]{0,19}
Description : Name of the Operations resource to return.
Type : string
folder
Location : path
Required : Yes
Description : Folder ID for this request.
Type : string
Pattern : folders/[0-9]{0,20}
Scopes :
▼ ▲ compute.folderZoneVmExtensionPolicies.delete
Path : {+folder}/zones/{zone}/vmExtensionPolicies/{vmExtensionPolicy}
Flat Path : folders/{foldersId}/zones/{zone}/vmExtensionPolicies/{vmExtensionPolicy}
Parameter Order :
Apiversion : 2026-10-01-preview
Description : Deletes a specified zone VM extension policy within a folder.
HTTP Method : DELETE
Parameters :
zone
Location : path
Required : Yes
Type : string
Description : Name of the zone for this request.
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
vmExtensionPolicy
Description : Name of the zone VM extension policy to delete.
Location : path
Required : Yes
Type : string
folder
Description : Folder ID for this request.
Location : path
Required : Yes
Type : string
Pattern : folders/[0-9]{0,20}
requestId
Description : An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments. The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000).
Type : string
Location : query
Scopes :
▼ ▲ compute.folderZoneVmExtensionPolicies.getVmExtension
HTTP Method : GET
Parameters :
zone
Description : Name of the zone for this request.
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
Location : path
Required : Yes
Type : string
folder
Pattern : folders/[0-9]{0,20}
Type : string
Description : Folder ID for this request.
Location : path
Required : Yes
extensionName
Description : Required. Name of the VM extension for this request.
Type : string
Location : path
Required : Yes
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?|[1-9][0-9]{0,19}
Scopes :
Apiversion : 2026-10-01-preview
Parameter Order :
Description : Retrieves details of a specific VM extension within a folder.
Flat Path : folders/{foldersId}/zones/{zone}/vmExtensions/{extensionName}
Path : {+folder}/zones/{zone}/vmExtensions/{extensionName}
▼ ▲ compute.folderZoneVmExtensionPolicies.list
Description : Lists all VM extension policies within a specific zone for a folder.
Flat Path : folders/{foldersId}/zones/{zone}/vmExtensionPolicies
Parameter Order :
Scopes :
Path : {+folder}/zones/{zone}/vmExtensionPolicies
HTTP Method : GET
Parameters :
zone
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
Type : string
Description : Name of the zone for this request.
Location : path
Required : Yes
folder
Description : Folder ID for this request.
Location : path
Required : Yes
Pattern : folders/[0-9]{0,20}
Type : string
filter
Description : A filter expression that filters resources listed in the response. Most Compute resources support two types of filter expressions: expressions that support regular expressions and expressions that follow API improvement proposal AIP-160. These two types of filter expressions cannot be mixed in one request. If you want to use AIP-160, your expression must specify the field name, an operator, and the value that you want to use for filtering. The value must be a string, a number, or a boolean. The operator must be either `=`, `!=`, `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute Engine instances, you can exclude instances named `example-instance` by specifying `name != example-instance`. The `:*` comparison can be used to test whether a key has been defined. For example, to find all objects with `owner` label use: ``` labels.owner:* ``` You can also filter nested fields. For example, you could specify `scheduling.automaticRestart = false` to include instances only if they are not scheduled for automatic restarts. You can use filtering on nested fields to filter based onresource labels. To filter on multiple expressions, provide each separate expression within parentheses. For example: ``` (scheduling.automaticRestart = true) (cpuPlatform = "Intel Skylake") ``` By default, each expression is an `AND` expression. However, you can include `AND` and `OR` expressions explicitly. For example: ``` (cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.automaticRestart = true) ``` If you want to use a regular expression, use the `eq` (equal) or `ne` (not equal) operator against a single un-parenthesized expression with or without quotes or against multiple parenthesized expressions. Examples: `fieldname eq unquoted literal` `fieldname eq 'single quoted literal'` `fieldname eq "double quoted literal"` `(fieldname1 eq literal) (fieldname2 ne "literal")` The literal value is interpreted as a regular expression using GoogleRE2 library syntax. The literal value must match the entire field. For example, to filter for instances that do not end with name "instance", you would use `name ne .*instance`. You cannot combine constraints on multiple fields using regular expressions.
Type : string
Location : query
orderBy
Location : query
Type : string
Description : Sorts list results by a certain order. By default, results are returned in alphanumerical order based on the resource name. You can also sort results in descending order based on the creation timestamp using `orderBy="creationTimestamp desc"`. This sorts results based on the `creationTimestamp` field in reverse chronological order (newest result first). Use this to sort resources like operations so that the newest operation is returned first. Currently, only sorting by `name` or `creationTimestamp desc` is supported.
maxResults
Minimum : 0
Description : The maximum number of results per page that should be returned. If the number of available results is larger than `maxResults`, Compute Engine returns a `nextPageToken` that can be used to get the next page of results in subsequent list requests. Acceptable values are `0` to `500`, inclusive. (Default: `500`)
Default : 500
Format : uint32
Location : query
Type : integer
pageToken
Type : string
Location : query
Description : Specifies a page token to use. Set `pageToken` to the `nextPageToken` returned by a previous list request to get the next page of results.
Apiversion : 2026-10-01-preview
▼ ▲ compute.folderZoneVmExtensionPolicies.insert
Scopes :
Description : Creates a new zone-level VM extension policy within a folder.
HTTP Method : POST
Parameters :
zone
Description : Name of the zone for this request.
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
Type : string
Location : path
Required : Yes
folder
Pattern : folders/[0-9]{0,20}
Location : path
Required : Yes
Description : Folder ID for this request.
Type : string
requestId
Description : An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments. The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000).
Type : string
Location : query
Path : {+folder}/zones/{zone}/vmExtensionPolicies
Flat Path : folders/{foldersId}/zones/{zone}/vmExtensionPolicies
Apiversion : 2026-10-01-preview
Parameter Order :
▼ ▲ compute.folderZoneVmExtensionPolicies.update
Scopes :
Path : {+folder}/zones/{zone}/vmExtensionPolicies/{vmExtensionPolicy}
Description : Modifies an existing zone VM extension policy within a folder.
Parameter Order :
Apiversion : 2026-10-01-preview
Flat Path : folders/{foldersId}/zones/{zone}/vmExtensionPolicies/{vmExtensionPolicy}
HTTP Method : PATCH
Parameters :
requestId
Location : query
Type : string
Description : An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments. The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000).
zone
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
Location : path
Required : Yes
Type : string
Description : Name of the zone for this request.
vmExtensionPolicy
Location : path
Required : Yes
Type : string
Description : Name of the zone VM extension policy to update.
folder
Pattern : folders/[0-9]{0,20}
Location : path
Required : Yes
Type : string
Description : Folder ID for this request.
▼ ▲ compute.folderZoneVmExtensionPolicies.get
Parameter Order :
Flat Path : folders/{foldersId}/zones/{zone}/vmExtensionPolicies/{vmExtensionPolicy}
Description : Retrieves details of a specific zone VM extension policy within a folder.
Apiversion : 2026-10-01-preview
Scopes :
Path : {+folder}/zones/{zone}/vmExtensionPolicies/{vmExtensionPolicy}
HTTP Method : GET
Parameters :
zone
Type : string
Location : path
Required : Yes
Description : Name of the zone for this request.
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
folder
Description : Folder ID for this request.
Pattern : folders/[0-9]{0,20}
Type : string
Location : path
Required : Yes
vmExtensionPolicy
Location : path
Required : Yes
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?|[1-9][0-9]{0,19}
Type : string
Description : Name of the VM extension policy resource to return.
▼ ▲ compute.folderZoneVmExtensionPolicies.listVmExtensions
Scopes :
Flat Path : folders/{foldersId}/zones/{zone}/vmExtensions
Path : {+folder}/zones/{zone}/vmExtensions
Description : Lists all VM extensions within a specific zone for a folder. This is a read-only API.
Apiversion : 2026-10-01-preview
Parameter Order :
HTTP Method : GET
Parameters :
pageToken
Description : Specifies a page token to use. Set `pageToken` to the `nextPageToken` returned by a previous list request to get the next page of results.
Type : string
Location : query
orderBy
Location : query
Type : string
Description : Sorts list results by a certain order. By default, results are returned in alphanumerical order based on the resource name. You can also sort results in descending order based on the creation timestamp using `orderBy="creationTimestamp desc"`. This sorts results based on the `creationTimestamp` field in reverse chronological order (newest result first). Use this to sort resources like operations so that the newest operation is returned first. Currently, only sorting by `name` or `creationTimestamp desc` is supported.
folder
Pattern : folders/[0-9]{0,20}
Type : string
Description : Folder ID for this request.
Location : path
Required : Yes
zone
Type : string
Description : Name of the zone for this request.
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
Location : path
Required : Yes
maxResults
Location : query
Format : uint32
Type : integer
Minimum : 0
Description : The maximum number of results per page that should be returned. If the number of available results is larger than `maxResults`, Compute Engine returns a `nextPageToken` that can be used to get the next page of results in subsequent list requests. Acceptable values are `0` to `500`, inclusive. (Default: `500`)
Default : 500
filter
Description : A filter expression that filters resources listed in the response. Most Compute resources support two types of filter expressions: expressions that support regular expressions and expressions that follow API improvement proposal AIP-160. These two types of filter expressions cannot be mixed in one request. If you want to use AIP-160, your expression must specify the field name, an operator, and the value that you want to use for filtering. The value must be a string, a number, or a boolean. The operator must be either `=`, `!=`, `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute Engine instances, you can exclude instances named `example-instance` by specifying `name != example-instance`. The `:*` comparison can be used to test whether a key has been defined. For example, to find all objects with `owner` label use: ``` labels.owner:* ``` You can also filter nested fields. For example, you could specify `scheduling.automaticRestart = false` to include instances only if they are not scheduled for automatic restarts. You can use filtering on nested fields to filter based onresource labels. To filter on multiple expressions, provide each separate expression within parentheses. For example: ``` (scheduling.automaticRestart = true) (cpuPlatform = "Intel Skylake") ``` By default, each expression is an `AND` expression. However, you can include `AND` and `OR` expressions explicitly. For example: ``` (cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.automaticRestart = true) ``` If you want to use a regular expression, use the `eq` (equal) or `ne` (not equal) operator against a single un-parenthesized expression with or without quotes or against multiple parenthesized expressions. Examples: `fieldname eq unquoted literal` `fieldname eq 'single quoted literal'` `fieldname eq "double quoted literal"` `(fieldname1 eq literal) (fieldname2 ne "literal")` The literal value is interpreted as a regular expression using GoogleRE2 library syntax. The literal value must match the entire field. For example, to filter for instances that do not end with name "instance", you would use `name ne .*instance`. You cannot combine constraints on multiple fields using regular expressions.
Location : query
Type : string
▼ ▲ compute.zoneFolderOperations.get
HTTP Method : GET
Parameters :
folder
Location : path
Required : Yes
Description : Folder ID for this request.
Type : string
Pattern : folders/[0-9]{0,20}
operation
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?|[1-9][0-9]{0,19}
Type : string
Description : Name of the Operations resource to return.
Location : path
Required : Yes
zone
Location : path
Required : Yes
Type : string
Description : Name of the zone for this request.
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
Apiversion : 2026-10-01-preview
Description : Retrieves the specified Operations resource.
Flat Path : folders/{foldersId}/zones/{zone}/operations/{operation}
Scopes :
Path : {+folder}/zones/{zone}/operations/{operation}
Parameter Order :
▼ ▲ compute.zoneFolderOperations.list
Scopes :
Apiversion : 2026-10-01-preview
Flat Path : folders/{foldersId}/zones/{zone}/operations
HTTP Method : GET
Parameters :
pageToken
Type : string
Location : query
Description : Specifies a page token to use. Set `pageToken` to the `nextPageToken` returned by a previous list request to get the next page of results.
filter
Location : query
Description : A filter expression that filters resources listed in the response. Most Compute resources support two types of filter expressions: expressions that support regular expressions and expressions that follow API improvement proposal AIP-160. These two types of filter expressions cannot be mixed in one request. If you want to use AIP-160, your expression must specify the field name, an operator, and the value that you want to use for filtering. The value must be a string, a number, or a boolean. The operator must be either `=`, `!=`, `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute Engine instances, you can exclude instances named `example-instance` by specifying `name != example-instance`. The `:*` comparison can be used to test whether a key has been defined. For example, to find all objects with `owner` label use: ``` labels.owner:* ``` You can also filter nested fields. For example, you could specify `scheduling.automaticRestart = false` to include instances only if they are not scheduled for automatic restarts. You can use filtering on nested fields to filter based onresource labels. To filter on multiple expressions, provide each separate expression within parentheses. For example: ``` (scheduling.automaticRestart = true) (cpuPlatform = "Intel Skylake") ``` By default, each expression is an `AND` expression. However, you can include `AND` and `OR` expressions explicitly. For example: ``` (cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.automaticRestart = true) ``` If you want to use a regular expression, use the `eq` (equal) or `ne` (not equal) operator against a single un-parenthesized expression with or without quotes or against multiple parenthesized expressions. Examples: `fieldname eq unquoted literal` `fieldname eq 'single quoted literal'` `fieldname eq "double quoted literal"` `(fieldname1 eq literal) (fieldname2 ne "literal")` The literal value is interpreted as a regular expression using GoogleRE2 library syntax. The literal value must match the entire field. For example, to filter for instances that do not end with name "instance", you would use `name ne .*instance`. You cannot combine constraints on multiple fields using regular expressions.
Type : string
orderBy
Type : string
Description : Sorts list results by a certain order. By default, results are returned in alphanumerical order based on the resource name. You can also sort results in descending order based on the creation timestamp using `orderBy="creationTimestamp desc"`. This sorts results based on the `creationTimestamp` field in reverse chronological order (newest result first). Use this to sort resources like operations so that the newest operation is returned first. Currently, only sorting by `name` or `creationTimestamp desc` is supported.
Location : query
zone
Type : string
Description : Name of the zone for request.
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
Location : path
Required : Yes
folder
Location : path
Required : Yes
Pattern : folders/[0-9]{0,20}
Type : string
Description : Folder ID for this request.
maxResults
Description : The maximum number of results per page that should be returned. If the number of available results is larger than `maxResults`, Compute Engine returns a `nextPageToken` that can be used to get the next page of results in subsequent list requests. Acceptable values are `0` to `500`, inclusive. (Default: `500`)
Location : query
Minimum : 0
Default : 500
Format : uint32
Type : integer
Parameter Order :
Description : Retrieves a list of Operation resources contained within the specified folder.
Path : {+folder}/zones/{zone}/operations
▼ ▲ compute.networks.updateNetworkProfile
Scopes :
Description : Updates the network profile of the specified network. Currently only the following operations are supported: - Removing a Regionally Bound Network Profile
Path : projects/{project}/global/networks/{network}/updateNetworkProfile
Flat Path : projects/{project}/global/networks/{network}/updateNetworkProfile
Apiversion : 2026-10-01-preview
HTTP Method : POST
Parameters :
requestId
Type : string
Description : An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments. The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000).
Location : query
network
Type : string
Location : path
Required : Yes
Description : Name of the network resource to update the network profile for.
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?|[1-9][0-9]{0,19}
project
Type : string
Location : path
Required : Yes
Description : Project ID for this request.
Pattern : (?:(?:[-a-z0-9]{1,63}\.)*(?:[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?):)?(?:[0-9]{1,19}|(?:[a-z0-9](?:[-a-z0-9]{0,61}[a-z0-9])?))
Parameter Order :
▼ ▲ compute.regionSslCertificates.fetchEncryptionKey
Scopes :
Flat Path : projects/{project}/regions/{region}/sslCertificates/encryptionKey
Description : Returns the public encryption key used to encrypt the TLS private key before upload.
Apiversion : 2026-10-01-preview
Parameter Order :
HTTP Method : GET
Parameters :
region
Type : string
Description : Name of the region scoping this request.
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
Location : path
Required : Yes
project
Type : string
Pattern : (?:(?:[-a-z0-9]{1,63}\.)*(?:[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?):)?(?:[0-9]{1,19}|(?:[a-z0-9](?:[-a-z0-9]{0,61}[a-z0-9])?))
Description : Project ID for this request.
Location : path
Required : Yes
Path : projects/{project}/regions/{region}/sslCertificates/encryptionKey
▼ ▲ compute.folderGlobalVmExtensionPolicies.getVmExtension
Parameter Order :
Description : Retrieves details of a specific VM extension.
Scopes :
Flat Path : folders/{foldersId}/global/vmExtensions/{extensionName}
Path : {+folder}/global/vmExtensions/{extensionName}
HTTP Method : GET
Parameters :
folder
Pattern : folders/[0-9]{0,20}
Location : path
Required : Yes
Description : Folder ID for this request.
Type : string
extensionName
Description : Required. Name of the VM extension for this request.
Type : string
Location : path
Required : Yes
Apiversion : 2026-10-01-preview
▼ ▲ compute.folderGlobalVmExtensionPolicies.delete
Flat Path : folders/{foldersId}/global/vmExtensionPolicies/{globalVmExtensionPolicy}/delete
Parameter Order :
Description : Purge scoped resources (zonal policies) from a folder level global VM extension policy, and then delete the global VM extension policy. Purge of the scoped resources is a pre-condition of the global VM extension policy deletion. The deletion of the global VM extension policy happens after the purge rollout is done, so it's not a part of the LRO. It's an automatic process that triggers in the backend.
Scopes :
Path : {+folder}/global/vmExtensionPolicies/{globalVmExtensionPolicy}/delete
HTTP Method : POST
Parameters :
folder
Location : path
Required : Yes
Type : string
Pattern : folders/[0-9]{0,20}
Description : Folder ID for this request.
requestId
Location : query
Description : An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments. The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000).
Type : string
globalVmExtensionPolicy
Location : path
Required : Yes
Description : Name of the global VM extension policy to purge scoped resources for.
Type : string
Apiversion : 2026-10-01-preview
▼ ▲ compute.folderGlobalVmExtensionPolicies.get
HTTP Method : GET
Parameters :
folder
Type : string
Description : Folder ID for this request.
Pattern : folders/[0-9]{0,20}
Location : path
Required : Yes
globalVmExtensionPolicy
Description : Name of the GlobalVmExtensionPolicy resource to return.
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?|[1-9][0-9]{0,19}
Location : path
Required : Yes
Type : string
Scopes :
Parameter Order :
Apiversion : 2026-10-01-preview
Flat Path : folders/{foldersId}/global/vmExtensionPolicies/{globalVmExtensionPolicy}
Path : {+folder}/global/vmExtensionPolicies/{globalVmExtensionPolicy}
Description : Gets details of a folder level GlobalVmExtensionPolicy.
▼ ▲ compute.folderGlobalVmExtensionPolicies.list
Path : {+folder}/global/vmExtensionPolicies
HTTP Method : GET
Parameters :
orderBy
Type : string
Location : query
Description : Sorts list results by a certain order. By default, results are returned in alphanumerical order based on the resource name. You can also sort results in descending order based on the creation timestamp using `orderBy="creationTimestamp desc"`. This sorts results based on the `creationTimestamp` field in reverse chronological order (newest result first). Use this to sort resources like operations so that the newest operation is returned first. Currently, only sorting by `name` or `creationTimestamp desc` is supported.
maxResults
Description : The maximum number of results per page that should be returned. If the number of available results is larger than `maxResults`, Compute Engine returns a `nextPageToken` that can be used to get the next page of results in subsequent list requests. Acceptable values are `0` to `500`, inclusive. (Default: `500`)
Location : query
Default : 500
Type : integer
Format : uint32
Minimum : 0
pageToken
Type : string
Description : Specifies a page token to use. Set `pageToken` to the `nextPageToken` returned by a previous list request to get the next page of results.
Location : query
filter
Location : query
Type : string
Description : A filter expression that filters resources listed in the response. Most Compute resources support two types of filter expressions: expressions that support regular expressions and expressions that follow API improvement proposal AIP-160. These two types of filter expressions cannot be mixed in one request. If you want to use AIP-160, your expression must specify the field name, an operator, and the value that you want to use for filtering. The value must be a string, a number, or a boolean. The operator must be either `=`, `!=`, `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute Engine instances, you can exclude instances named `example-instance` by specifying `name != example-instance`. The `:*` comparison can be used to test whether a key has been defined. For example, to find all objects with `owner` label use: ``` labels.owner:* ``` You can also filter nested fields. For example, you could specify `scheduling.automaticRestart = false` to include instances only if they are not scheduled for automatic restarts. You can use filtering on nested fields to filter based onresource labels. To filter on multiple expressions, provide each separate expression within parentheses. For example: ``` (scheduling.automaticRestart = true) (cpuPlatform = "Intel Skylake") ``` By default, each expression is an `AND` expression. However, you can include `AND` and `OR` expressions explicitly. For example: ``` (cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.automaticRestart = true) ``` If you want to use a regular expression, use the `eq` (equal) or `ne` (not equal) operator against a single un-parenthesized expression with or without quotes or against multiple parenthesized expressions. Examples: `fieldname eq unquoted literal` `fieldname eq 'single quoted literal'` `fieldname eq "double quoted literal"` `(fieldname1 eq literal) (fieldname2 ne "literal")` The literal value is interpreted as a regular expression using GoogleRE2 library syntax. The literal value must match the entire field. For example, to filter for instances that do not end with name "instance", you would use `name ne .*instance`. You cannot combine constraints on multiple fields using regular expressions.
folder
Description : Folder ID for this request.
Type : string
Pattern : folders/[0-9]{0,20}
Location : path
Required : Yes
Flat Path : folders/{foldersId}/global/vmExtensionPolicies
Apiversion : 2026-10-01-preview
Scopes :
Parameter Order : folder
Description : Lists folder level GlobalVmExtensionPolicies.
▼ ▲ compute.folderGlobalVmExtensionPolicies.aggregatedList
Parameter Order : folder
Path : {+folder}/aggregated/vmExtensionPolicies
Flat Path : folders/{foldersId}/aggregated/vmExtensionPolicies
Apiversion : 2026-10-01-preview
HTTP Method : GET
Parameters :
orderBy
Description : Sorts list results by a certain order. By default, results are returned in alphanumerical order based on the resource name. You can also sort results in descending order based on the creation timestamp using `orderBy="creationTimestamp desc"`. This sorts results based on the `creationTimestamp` field in reverse chronological order (newest result first). Use this to sort resources like operations so that the newest operation is returned first. Currently, only sorting by `name` or `creationTimestamp desc` is supported.
Location : query
Type : string
folder
Pattern : folders/[0-9]{0,20}
Location : path
Required : Yes
Description : Folder ID for this request.
Type : string
maxResults
Format : uint32
Location : query
Minimum : 0
Default : 500
Type : integer
Description : The maximum number of results per page that should be returned. If the number of available results is larger than `maxResults`, Compute Engine returns a `nextPageToken` that can be used to get the next page of results in subsequent list requests. Acceptable values are `0` to `500`, inclusive. (Default: `500`)
filter
Location : query
Type : string
Description : A filter expression that filters resources listed in the response. Most Compute resources support two types of filter expressions: expressions that support regular expressions and expressions that follow API improvement proposal AIP-160. These two types of filter expressions cannot be mixed in one request. If you want to use AIP-160, your expression must specify the field name, an operator, and the value that you want to use for filtering. The value must be a string, a number, or a boolean. The operator must be either `=`, `!=`, `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute Engine instances, you can exclude instances named `example-instance` by specifying `name != example-instance`. The `:*` comparison can be used to test whether a key has been defined. For example, to find all objects with `owner` label use: ``` labels.owner:* ``` You can also filter nested fields. For example, you could specify `scheduling.automaticRestart = false` to include instances only if they are not scheduled for automatic restarts. You can use filtering on nested fields to filter based onresource labels. To filter on multiple expressions, provide each separate expression within parentheses. For example: ``` (scheduling.automaticRestart = true) (cpuPlatform = "Intel Skylake") ``` By default, each expression is an `AND` expression. However, you can include `AND` and `OR` expressions explicitly. For example: ``` (cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.automaticRestart = true) ``` If you want to use a regular expression, use the `eq` (equal) or `ne` (not equal) operator against a single un-parenthesized expression with or without quotes or against multiple parenthesized expressions. Examples: `fieldname eq unquoted literal` `fieldname eq 'single quoted literal'` `fieldname eq "double quoted literal"` `(fieldname1 eq literal) (fieldname2 ne "literal")` The literal value is interpreted as a regular expression using GoogleRE2 library syntax. The literal value must match the entire field. For example, to filter for instances that do not end with name "instance", you would use `name ne .*instance`. You cannot combine constraints on multiple fields using regular expressions.
serviceProjectNumber
Location : query
Description : The Shared VPC service project id or service project number for which aggregated list request is invoked for subnetworks list-usable api.
Type : string
Format : int64
includeAllScopes
Type : boolean
Location : query
Description : Indicates whether every visible scope for each scope type (zone, region, global) should be included in the response. For new resource types added after this field, the flag has no effect as new resource types will always include every visible scope for each scope type in response. For resource types which predate this field, if this flag is omitted or false, only scopes of the scope types where the resource type is expected to be found will be included.
pageToken
Description : Specifies a page token to use. Set `pageToken` to the `nextPageToken` returned by a previous list request to get the next page of results.
Type : string
Location : query
Description : Retrieves the list of all folder level VM Extension Policy resources available to the specified folder. To prevent failure, it's recommended that you set the `returnPartialSuccess` parameter to `true`.
Scopes :
▼ ▲ compute.folderGlobalVmExtensionPolicies.listVmExtensions
Scopes :
Path : {+folder}/global/vmExtensions
Apiversion : 2026-10-01-preview
Parameter Order : folder
Description : Lists all VM extensions within a folder. This is a read-only API.
HTTP Method : GET
Parameters :
folder
Description : Required. Folder ID for this request.
Location : path
Required : Yes
Type : string
Pattern : folders/[0-9]{0,20}
maxResults
Type : integer
Location : query
Format : uint32
Description : The maximum number of results per page that should be returned. If the number of available results is larger than `maxResults`, Compute Engine returns a `nextPageToken` that can be used to get the next page of results in subsequent list requests. Acceptable values are `0` to `500`, inclusive. (Default: `500`)
Minimum : 0
Default : 500
orderBy
Location : query
Type : string
Description : Sorts list results by a certain order. By default, results are returned in alphanumerical order based on the resource name. You can also sort results in descending order based on the creation timestamp using `orderBy="creationTimestamp desc"`. This sorts results based on the `creationTimestamp` field in reverse chronological order (newest result first). Use this to sort resources like operations so that the newest operation is returned first. Currently, only sorting by `name` or `creationTimestamp desc` is supported.
pageToken
Location : query
Type : string
Description : Specifies a page token to use. Set `pageToken` to the `nextPageToken` returned by a previous list request to get the next page of results.
filter
Location : query
Description : A filter expression that filters resources listed in the response. Most Compute resources support two types of filter expressions: expressions that support regular expressions and expressions that follow API improvement proposal AIP-160. These two types of filter expressions cannot be mixed in one request. If you want to use AIP-160, your expression must specify the field name, an operator, and the value that you want to use for filtering. The value must be a string, a number, or a boolean. The operator must be either `=`, `!=`, `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute Engine instances, you can exclude instances named `example-instance` by specifying `name != example-instance`. The `:*` comparison can be used to test whether a key has been defined. For example, to find all objects with `owner` label use: ``` labels.owner:* ``` You can also filter nested fields. For example, you could specify `scheduling.automaticRestart = false` to include instances only if they are not scheduled for automatic restarts. You can use filtering on nested fields to filter based onresource labels. To filter on multiple expressions, provide each separate expression within parentheses. For example: ``` (scheduling.automaticRestart = true) (cpuPlatform = "Intel Skylake") ``` By default, each expression is an `AND` expression. However, you can include `AND` and `OR` expressions explicitly. For example: ``` (cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.automaticRestart = true) ``` If you want to use a regular expression, use the `eq` (equal) or `ne` (not equal) operator against a single un-parenthesized expression with or without quotes or against multiple parenthesized expressions. Examples: `fieldname eq unquoted literal` `fieldname eq 'single quoted literal'` `fieldname eq "double quoted literal"` `(fieldname1 eq literal) (fieldname2 ne "literal")` The literal value is interpreted as a regular expression using GoogleRE2 library syntax. The literal value must match the entire field. For example, to filter for instances that do not end with name "instance", you would use `name ne .*instance`. You cannot combine constraints on multiple fields using regular expressions.
Type : string
Flat Path : folders/{foldersId}/global/vmExtensions
▼ ▲ compute.folderGlobalVmExtensionPolicies.insert
Path : {+folder}/global/vmExtensionPolicies
Parameter Order : folder
Description : Creates a new folder level GlobalVmExtensionPolicy.
Apiversion : 2026-10-01-preview
Flat Path : folders/{foldersId}/global/vmExtensionPolicies
HTTP Method : POST
Parameters :
folder
Pattern : folders/[0-9]{0,20}
Type : string
Description : Folder ID for this request.
Location : path
Required : Yes
requestId
Location : query
Type : string
Description : An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments. The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000).
Scopes :
▼ ▲ compute.folderGlobalVmExtensionPolicies.update
Parameter Order :
Description : Updates a folder level GlobalVmExtensionPolicy.
Path : {+folder}/global/vmExtensionPolicies/{globalVmExtensionPolicy}
Flat Path : folders/{foldersId}/global/vmExtensionPolicies/{globalVmExtensionPolicy}
HTTP Method : PATCH
Parameters :
requestId
Description : An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments. The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000).
Location : query
Type : string
folder
Location : path
Required : Yes
Description : Folder ID for this request.
Type : string
Pattern : folders/[0-9]{0,20}
globalVmExtensionPolicy
Description : Name of the global VM extension policy to update.
Type : string
Location : path
Required : Yes
Apiversion : 2026-10-01-preview
Scopes :
▼ ▲ compute.organizationZoneVmExtensionPolicies.listVmExtensions
Apiversion : 2026-10-01-preview
Scopes :
Parameter Order :
HTTP Method : GET
Parameters :
maxResults
Minimum : 0
Format : uint32
Default : 500
Type : integer
Location : query
Description : The maximum number of results per page that should be returned. If the number of available results is larger than `maxResults`, Compute Engine returns a `nextPageToken` that can be used to get the next page of results in subsequent list requests. Acceptable values are `0` to `500`, inclusive. (Default: `500`)
filter
Type : string
Location : query
Description : A filter expression that filters resources listed in the response. Most Compute resources support two types of filter expressions: expressions that support regular expressions and expressions that follow API improvement proposal AIP-160. These two types of filter expressions cannot be mixed in one request. If you want to use AIP-160, your expression must specify the field name, an operator, and the value that you want to use for filtering. The value must be a string, a number, or a boolean. The operator must be either `=`, `!=`, `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute Engine instances, you can exclude instances named `example-instance` by specifying `name != example-instance`. The `:*` comparison can be used to test whether a key has been defined. For example, to find all objects with `owner` label use: ``` labels.owner:* ``` You can also filter nested fields. For example, you could specify `scheduling.automaticRestart = false` to include instances only if they are not scheduled for automatic restarts. You can use filtering on nested fields to filter based onresource labels. To filter on multiple expressions, provide each separate expression within parentheses. For example: ``` (scheduling.automaticRestart = true) (cpuPlatform = "Intel Skylake") ``` By default, each expression is an `AND` expression. However, you can include `AND` and `OR` expressions explicitly. For example: ``` (cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.automaticRestart = true) ``` If you want to use a regular expression, use the `eq` (equal) or `ne` (not equal) operator against a single un-parenthesized expression with or without quotes or against multiple parenthesized expressions. Examples: `fieldname eq unquoted literal` `fieldname eq 'single quoted literal'` `fieldname eq "double quoted literal"` `(fieldname1 eq literal) (fieldname2 ne "literal")` The literal value is interpreted as a regular expression using GoogleRE2 library syntax. The literal value must match the entire field. For example, to filter for instances that do not end with name "instance", you would use `name ne .*instance`. You cannot combine constraints on multiple fields using regular expressions.
organization
Description : Organization ID for this request.
Location : path
Required : Yes
Pattern : organizations/[0-9]{0,20}
Type : string
zone
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
Type : string
Description : Name of the zone for this request.
Location : path
Required : Yes
orderBy
Description : Sorts list results by a certain order. By default, results are returned in alphanumerical order based on the resource name. You can also sort results in descending order based on the creation timestamp using `orderBy="creationTimestamp desc"`. This sorts results based on the `creationTimestamp` field in reverse chronological order (newest result first). Use this to sort resources like operations so that the newest operation is returned first. Currently, only sorting by `name` or `creationTimestamp desc` is supported.
Location : query
Type : string
pageToken
Description : Specifies a page token to use. Set `pageToken` to the `nextPageToken` returned by a previous list request to get the next page of results.
Location : query
Type : string
Path : {+organization}/zones/{zone}/vmExtensions
Flat Path : organizations/{organizationsId}/zones/{zone}/vmExtensions
Description : Lists all VM extensions within a specific zone for an organization. This is a read-only API.
▼ ▲ compute.organizationZoneVmExtensionPolicies.getVmExtension
Flat Path : organizations/{organizationsId}/zones/{zone}/vmExtensions/{extensionName}
Parameter Order :
Path : {+organization}/zones/{zone}/vmExtensions/{extensionName}
Description : Retrieves details of a specific VM extension within an organization.
HTTP Method : GET
Parameters :
extensionName
Description : Required. Name of the VM extension for this request.
Location : path
Required : Yes
Type : string
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?|[1-9][0-9]{0,19}
zone
Type : string
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
Location : path
Required : Yes
Description : Name of the zone for this request.
organization
Description : Organization ID for this request.
Type : string
Pattern : organizations/[0-9]{0,20}
Location : path
Required : Yes
Scopes :
Apiversion : 2026-10-01-preview
▼ ▲ compute.organizationZoneVmExtensionPolicies.get
Parameter Order :
Scopes :
Flat Path : organizations/{organizationsId}/zones/{zone}/vmExtensionPolicies/{vmExtensionPolicy}
Description : Retrieves details of a specific zone VM extension policy within an organization.
HTTP Method : GET
Parameters :
zone
Location : path
Required : Yes
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
Description : Name of the zone for this request.
Type : string
vmExtensionPolicy
Location : path
Required : Yes
Type : string
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?|[1-9][0-9]{0,19}
Description : Name of the VM extension policy resource to return.
organization
Description : Organization ID for this request.
Pattern : organizations/[0-9]{0,20}
Location : path
Required : Yes
Type : string
Path : {+organization}/zones/{zone}/vmExtensionPolicies/{vmExtensionPolicy}
Apiversion : 2026-10-01-preview
▼ ▲ compute.organizationZoneVmExtensionPolicies.delete
Parameter Order :
Scopes :
Path : {+organization}/zones/{zone}/vmExtensionPolicies/{vmExtensionPolicy}
HTTP Method : DELETE
Parameters :
zone
Type : string
Location : path
Required : Yes
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
Description : Name of the zone for this request.
organization
Type : string
Description : Organization ID for this request.
Location : path
Required : Yes
Pattern : organizations/[0-9]{0,20}
requestId
Type : string
Location : query
Description : An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments. The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000).
vmExtensionPolicy
Location : path
Required : Yes
Type : string
Description : Name of the zone VM extension policy to delete.
Flat Path : organizations/{organizationsId}/zones/{zone}/vmExtensionPolicies/{vmExtensionPolicy}
Description : Deletes a specified zone VM extension policy within an organization.
Apiversion : 2026-10-01-preview
▼ ▲ compute.organizationZoneVmExtensionPolicies.list
Parameter Order :
Flat Path : organizations/{organizationsId}/zones/{zone}/vmExtensionPolicies
Scopes :
Description : Lists all VM extension policies within a specific zone for an organization.
HTTP Method : GET
Parameters :
filter
Location : query
Type : string
Description : A filter expression that filters resources listed in the response. Most Compute resources support two types of filter expressions: expressions that support regular expressions and expressions that follow API improvement proposal AIP-160. These two types of filter expressions cannot be mixed in one request. If you want to use AIP-160, your expression must specify the field name, an operator, and the value that you want to use for filtering. The value must be a string, a number, or a boolean. The operator must be either `=`, `!=`, `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute Engine instances, you can exclude instances named `example-instance` by specifying `name != example-instance`. The `:*` comparison can be used to test whether a key has been defined. For example, to find all objects with `owner` label use: ``` labels.owner:* ``` You can also filter nested fields. For example, you could specify `scheduling.automaticRestart = false` to include instances only if they are not scheduled for automatic restarts. You can use filtering on nested fields to filter based onresource labels. To filter on multiple expressions, provide each separate expression within parentheses. For example: ``` (scheduling.automaticRestart = true) (cpuPlatform = "Intel Skylake") ``` By default, each expression is an `AND` expression. However, you can include `AND` and `OR` expressions explicitly. For example: ``` (cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.automaticRestart = true) ``` If you want to use a regular expression, use the `eq` (equal) or `ne` (not equal) operator against a single un-parenthesized expression with or without quotes or against multiple parenthesized expressions. Examples: `fieldname eq unquoted literal` `fieldname eq 'single quoted literal'` `fieldname eq "double quoted literal"` `(fieldname1 eq literal) (fieldname2 ne "literal")` The literal value is interpreted as a regular expression using GoogleRE2 library syntax. The literal value must match the entire field. For example, to filter for instances that do not end with name "instance", you would use `name ne .*instance`. You cannot combine constraints on multiple fields using regular expressions.
pageToken
Location : query
Type : string
Description : Specifies a page token to use. Set `pageToken` to the `nextPageToken` returned by a previous list request to get the next page of results.
maxResults
Location : query
Format : uint32
Default : 500
Description : The maximum number of results per page that should be returned. If the number of available results is larger than `maxResults`, Compute Engine returns a `nextPageToken` that can be used to get the next page of results in subsequent list requests. Acceptable values are `0` to `500`, inclusive. (Default: `500`)
Minimum : 0
Type : integer
zone
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
Description : Name of the zone for this request.
Location : path
Required : Yes
Type : string
organization
Location : path
Required : Yes
Pattern : organizations/[0-9]{0,20}
Type : string
Description : Organization ID for this request.
orderBy
Type : string
Location : query
Description : Sorts list results by a certain order. By default, results are returned in alphanumerical order based on the resource name. You can also sort results in descending order based on the creation timestamp using `orderBy="creationTimestamp desc"`. This sorts results based on the `creationTimestamp` field in reverse chronological order (newest result first). Use this to sort resources like operations so that the newest operation is returned first. Currently, only sorting by `name` or `creationTimestamp desc` is supported.
Path : {+organization}/zones/{zone}/vmExtensionPolicies
Apiversion : 2026-10-01-preview
▼ ▲ compute.organizationZoneVmExtensionPolicies.insert
HTTP Method : POST
Parameters :
organization
Description : Organization ID for this request.
Pattern : organizations/[0-9]{0,20}
Type : string
Location : path
Required : Yes
zone
Type : string
Location : path
Required : Yes
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
Description : Name of the zone for this request.
requestId
Description : An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments. The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000).
Location : query
Type : string
Apiversion : 2026-10-01-preview
Parameter Order :
Flat Path : organizations/{organizationsId}/zones/{zone}/vmExtensionPolicies
Path : {+organization}/zones/{zone}/vmExtensionPolicies
Description : Creates a new zone-level VM extension policy within an organization.
Scopes :
▼ ▲ compute.organizationZoneVmExtensionPolicies.update
Flat Path : organizations/{organizationsId}/zones/{zone}/vmExtensionPolicies/{vmExtensionPolicy}
HTTP Method : PATCH
Parameters :
zone
Type : string
Location : path
Required : Yes
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
Description : Name of the zone for this request.
requestId
Type : string
Location : query
Description : An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments. The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000).
organization
Pattern : organizations/[0-9]{0,20}
Location : path
Required : Yes
Type : string
Description : Organization ID for this request.
vmExtensionPolicy
Location : path
Required : Yes
Type : string
Description : Name of the zone VM extension policy to update.
Path : {+organization}/zones/{zone}/vmExtensionPolicies/{vmExtensionPolicy}
Apiversion : 2026-10-01-preview
Parameter Order :
Scopes :
Description : Modifies an existing zone VM extension policy within an organization.