2026-10-24
▼ ▲ compute.instances.troubleshoot
Parameter Order :
Scopes :
Apiversion : 2026-10-01-preview
Description : Initiates diagnostic troubleshooting on the specified instance. This operation cannot be cancelled.
Flat Path : projects/{project}/zones/{zone}/instances/{instance}/troubleshoot
Parameters :
instance
Required : Yes
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?|[1-9][0-9]{0,19}
Type : string
Location : path
Description : Name of the instance scoping this request.
params.endTime
Type : string
Description : Input only. Timestamp representing the end of the troubleshooting window in RFC3339 text format. If omitted, defaults to 'now'.
Location : query
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])?))
Location : path
Description : Project ID for this request.
zone
Location : path
Type : string
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
Description : The name of the zone for this request.
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).
params.startTime
Type : string
Location : query
Description : Input only. Timestamp representing the beginning of the troubleshooting window in RFC3339 text format. If omitted, defaults to the last 12 hours.
Path : projects/{project}/zones/{zone}/instances/{instance}/troubleshoot
HTTP Method : POST
▼ ▲ compute.instances.update
Parameters :
minimalAction
Enum RESTART_IN_PLACE
Enum Descriptions The instance will restart on the same host. Data on all local SSDs will be preserved.
mostDisruptiveAllowedAction
Enum Descriptions The instance will restart on the same host. Data on all local SSDs will be preserved.
Enum RESTART_IN_PLACE
▼ ▲ compute.globalVmExtensionPolicies.getVmExtension
HTTP Method : GET
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])?))
Type : string
Description : Project ID for this request.
extensionName
Location : path
Required : Yes
Type : string
Description : Required. Name of the VM extension for this request.
Apiversion : 2026-10-01-preview
Scopes :
Flat Path : projects/{project}/global/vmExtensions/{extensionName}
Path : projects/{project}/global/vmExtensions/{extensionName}
Parameter Order :
Description : Retrieves details of a specific VM extension.
▼ ▲ compute.globalVmExtensionPolicies.listVmExtensions
Apiversion : 2026-10-01-preview
HTTP Method : GET
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
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
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.
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
maxResults
Type : integer
Minimum : 0
Default : 500
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`)
Scopes :
Description : Lists all VM extensions within a specific zone for a project. This is a read-only API.
Flat Path : projects/{project}/global/vmExtensions
Parameter Order : project
Path : projects/{project}/global/vmExtensions
▼ ▲ compute.zoneOrganizationOperations.get
Apiversion : 2026-10-01-preview
Path : {+organization}/zones/{zone}/operations/{operation}
HTTP Method : GET
Parameters :
organization
Location : path
Required : Yes
Type : string
Description : Organization ID for this request.
Pattern : organizations/[0-9]{0,20}
operation
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?|[1-9][0-9]{0,19}
Type : string
Required : Yes
Description : Name of the Operations resource to return. Parent is derived from this field.
Location : path
zone
Type : string
Description : Name of the zone for this request.
Location : path
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
Required : Yes
Parameter Order :
Description : Retrieves the specified Operations resource.
Flat Path : organizations/{organizationsId}/zones/{zone}/operations/{operation}
Scopes :
▼ ▲ compute.zoneOrganizationOperations.list
Path : {+organization}/zones/{zone}/operations
Description : Retrieves a list of Operation resources contained within the specified organization.
Flat Path : organizations/{organizationsId}/zones/{zone}/operations
Apiversion : 2026-10-01-preview
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.
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.
maxResults
Format : uint32
Default : 500
Location : query
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`)
Type : integer
zone
Location : path
Required : Yes
Description : Name of the zone for request.
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
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
organization
Required : Yes
Type : string
Pattern : ^organizations/[^/]+$
Location : path
Description : Organization ID for this request.
Scopes :
Parameter Order :
▼ ▲ compute.folderGlobalVmExtensionPolicies.list
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.
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
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
folder
Location : path
Pattern : folders/[0-9]{0,20}
Description : Folder ID for this request.
Type : string
Required : Yes
Parameter Order : folder
Apiversion : 2026-10-01-preview
Path : {+folder}/global/vmExtensionPolicies
Scopes :
Description : Lists folder level GlobalVmExtensionPolicies.
Flat Path : folders/{foldersId}/global/vmExtensionPolicies
▼ ▲ compute.folderGlobalVmExtensionPolicies.getVmExtension
Flat Path : folders/{foldersId}/global/vmExtensions/{extensionName}
Parameter Order :
HTTP Method : GET
Parameters :
extensionName
Required : Yes
Description : Required. Name of the VM extension for this request.
Type : string
Location : path
folder
Location : path
Required : Yes
Description : Folder ID for this request.
Type : string
Pattern : folders/[0-9]{0,20}
Scopes :
Apiversion : 2026-10-01-preview
Path : {+folder}/global/vmExtensions/{extensionName}
Description : Retrieves details of a specific VM extension.
▼ ▲ compute.folderGlobalVmExtensionPolicies.delete
Path : {+folder}/global/vmExtensionPolicies/{globalVmExtensionPolicy}/delete
Parameter Order :
Flat Path : folders/{foldersId}/global/vmExtensionPolicies/{globalVmExtensionPolicy}/delete
HTTP Method : POST
Parameters :
folder
Type : string
Required : Yes
Pattern : folders/[0-9]{0,20}
Location : path
Description : Folder ID for this request.
globalVmExtensionPolicy
Location : path
Type : string
Description : Name of the global VM extension policy to purge scoped resources for.
Required : Yes
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
Scopes :
Apiversion : 2026-10-01-preview
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.
▼ ▲ 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`.
Scopes :
Flat Path : folders/{foldersId}/aggregated/vmExtensionPolicies
Path : {+folder}/aggregated/vmExtensionPolicies
Apiversion : 2026-10-01-preview
Parameter Order : folder
HTTP Method : GET
Parameters :
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.
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
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
Type : string
Location : path
Required : Yes
Pattern : folders/[0-9]{0,20}
Description : Folder ID for this request.
maxResults
Format : uint32
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`)
Location : query
Default : 500
Type : integer
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
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
▼ ▲ compute.folderGlobalVmExtensionPolicies.update
Parameter Order :
Path : {+folder}/global/vmExtensionPolicies/{globalVmExtensionPolicy}
Scopes :
Apiversion : 2026-10-01-preview
Description : Updates a folder level GlobalVmExtensionPolicy.
HTTP Method : PATCH
Parameters :
globalVmExtensionPolicy
Location : path
Type : string
Description : Name of the global VM extension policy to update.
Required : Yes
folder
Pattern : folders/[0-9]{0,20}
Description : Folder ID for this request.
Required : Yes
Location : path
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).
Flat Path : folders/{foldersId}/global/vmExtensionPolicies/{globalVmExtensionPolicy}
▼ ▲ compute.folderGlobalVmExtensionPolicies.get
Flat Path : folders/{foldersId}/global/vmExtensionPolicies/{globalVmExtensionPolicy}
HTTP Method : GET
Parameters :
folder
Type : string
Location : path
Description : Folder ID for this request.
Required : Yes
Pattern : folders/[0-9]{0,20}
globalVmExtensionPolicy
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 GlobalVmExtensionPolicy resource to return.
Apiversion : 2026-10-01-preview
Path : {+folder}/global/vmExtensionPolicies/{globalVmExtensionPolicy}
Scopes :
Description : Gets details of a folder level GlobalVmExtensionPolicy.
Parameter Order :
▼ ▲ compute.folderGlobalVmExtensionPolicies.listVmExtensions
Path : {+folder}/global/vmExtensions
Parameter Order : folder
Scopes :
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
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 : Required. Folder ID for this request.
Required : Yes
Type : string
Location : path
Pattern : folders/[0-9]{0,20}
maxResults
Location : query
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`)
Type : integer
Default : 500
Format : uint32
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
Flat Path : folders/{foldersId}/global/vmExtensions
Description : Lists all VM extensions within a folder. This is a read-only API.
▼ ▲ compute.folderGlobalVmExtensionPolicies.insert
Apiversion : 2026-10-01-preview
HTTP Method : POST
Parameters :
folder
Description : Folder ID for this request.
Location : path
Pattern : folders/[0-9]{0,20}
Required : Yes
Type : string
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 : {+folder}/global/vmExtensionPolicies
Parameter Order : folder
Scopes :
Description : Creates a new folder level GlobalVmExtensionPolicy.
Flat Path : folders/{foldersId}/global/vmExtensionPolicies
▼ ▲ compute.organizationZoneVmExtensionPolicies.get
Path : {+organization}/zones/{zone}/vmExtensionPolicies/{vmExtensionPolicy}
Flat Path : organizations/{organizationsId}/zones/{zone}/vmExtensionPolicies/{vmExtensionPolicy}
Parameter Order :
Description : Retrieves details of a specific zone VM extension policy within an organization.
Scopes :
HTTP Method : GET
Parameters :
vmExtensionPolicy
Location : path
Type : string
Required : Yes
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
Required : Yes
Type : string
Pattern : organizations/[0-9]{0,20}
Location : path
Description : Organization ID for this request.
zone
Required : Yes
Type : string
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
Location : path
Description : Name of the zone for this request.
Apiversion : 2026-10-01-preview
▼ ▲ compute.organizationZoneVmExtensionPolicies.update
Flat Path : organizations/{organizationsId}/zones/{zone}/vmExtensionPolicies/{vmExtensionPolicy}
Apiversion : 2026-10-01-preview
Description : Modifies an existing zone VM extension policy within an organization.
Scopes :
Parameter Order :
HTTP Method : PATCH
Parameters :
zone
Description : Name of the zone for this request.
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
Type : string
Required : Yes
Location : path
vmExtensionPolicy
Required : Yes
Description : Name of the zone VM extension policy to update.
Type : string
Location : path
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
Description : Organization ID for this request.
Pattern : organizations/[0-9]{0,20}
Required : Yes
Location : path
Type : string
Path : {+organization}/zones/{zone}/vmExtensionPolicies/{vmExtensionPolicy}
▼ ▲ compute.organizationZoneVmExtensionPolicies.getVmExtension
Flat Path : organizations/{organizationsId}/zones/{zone}/vmExtensions/{extensionName}
Parameter Order :
Description : Retrieves details of a specific VM extension within an organization.
Apiversion : 2026-10-01-preview
HTTP Method : GET
Parameters :
extensionName
Description : Required. Name of the VM extension for this request.
Location : path
Required : Yes
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?|[1-9][0-9]{0,19}
Type : string
organization
Description : Organization ID for this request.
Type : string
Location : path
Required : Yes
Pattern : organizations/[0-9]{0,20}
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
Scopes :
Path : {+organization}/zones/{zone}/vmExtensions/{extensionName}
▼ ▲ compute.organizationZoneVmExtensionPolicies.delete
Flat Path : organizations/{organizationsId}/zones/{zone}/vmExtensionPolicies/{vmExtensionPolicy}
HTTP Method : DELETE
Parameters :
organization
Type : string
Description : Organization ID for this request.
Location : path
Pattern : organizations/[0-9]{0,20}
Required : Yes
vmExtensionPolicy
Type : string
Location : path
Required : Yes
Description : Name of the zone VM extension policy to delete.
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).
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])?
Apiversion : 2026-10-01-preview
Path : {+organization}/zones/{zone}/vmExtensionPolicies/{vmExtensionPolicy}
Scopes :
Parameter Order :
Description : Deletes a specified zone VM extension policy within an organization.
▼ ▲ compute.organizationZoneVmExtensionPolicies.insert
Flat Path : organizations/{organizationsId}/zones/{zone}/vmExtensionPolicies
Path : {+organization}/zones/{zone}/vmExtensionPolicies
Apiversion : 2026-10-01-preview
Description : Creates a new zone-level VM extension policy within an organization.
HTTP Method : POST
Parameters :
zone
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
Description : Name of the zone for this request.
Type : string
Required : Yes
Location : path
organization
Pattern : organizations/[0-9]{0,20}
Type : string
Required : Yes
Description : Organization ID for this request.
Location : path
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 :
Scopes :
▼ ▲ compute.organizationZoneVmExtensionPolicies.listVmExtensions
Scopes :
Description : Lists all VM extensions within a specific zone for an organization. This is a read-only API.
Apiversion : 2026-10-01-preview
Parameter Order :
Flat Path : organizations/{organizationsId}/zones/{zone}/vmExtensions
HTTP Method : GET
Parameters :
organization
Description : Organization ID for this request.
Location : path
Type : string
Required : Yes
Pattern : organizations/[0-9]{0,20}
zone
Description : Name of the zone for this request.
Required : Yes
Location : path
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
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.
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
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.
maxResults
Location : query
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`)
Format : uint32
Minimum : 0
Path : {+organization}/zones/{zone}/vmExtensions
▼ ▲ compute.organizationZoneVmExtensionPolicies.list
Flat Path : organizations/{organizationsId}/zones/{zone}/vmExtensionPolicies
Description : Lists all VM extension policies within a specific zone for an organization.
Scopes :
Path : {+organization}/zones/{zone}/vmExtensionPolicies
Parameter Order :
Apiversion : 2026-10-01-preview
HTTP Method : GET
Parameters :
zone
Required : Yes
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
Location : path
Type : string
Description : Name of the zone for this request.
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
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.
organization
Type : string
Description : Organization ID for this request.
Location : path
Pattern : organizations/[0-9]{0,20}
Required : Yes
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`)
Type : integer
Format : uint32
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
▼ ▲ compute.zoneVmExtensionPolicies.getVmExtension
Flat Path : projects/{project}/zones/{zone}/vmExtensions/{extensionName}
Scopes :
Path : projects/{project}/zones/{zone}/vmExtensions/{extensionName}
Parameter Order :
HTTP Method : GET
Parameters :
zone
Description : Name of the zone for this request.
Required : Yes
Location : path
Type : string
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
extensionName
Description : Required. Name of the VM extension for this request.
Type : string
Location : path
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?|[1-9][0-9]{0,19}
Required : Yes
project
Location : path
Description : Project ID for this request.
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])?))
Apiversion : 2026-10-01-preview
Description : Retrieves details of a specific VM extension within a project.
▼ ▲ compute.zoneVmExtensionPolicies.listVmExtensions
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.
Location : query
Type : string
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])?))
Required : Yes
Location : path
Type : string
Description : Required. Project ID for this request.
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
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
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`)
Default : 500
Minimum : 0
Type : integer
Location : query
Format : uint32
zone
Type : string
Description : Name of the zone for this request.
Required : Yes
Location : path
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
Parameter Order :
Apiversion : 2026-10-01-preview
Path : projects/{project}/zones/{zone}/vmExtensions
Scopes :
Description : Lists all VM extensions within a specific zone for a project. This is a read-only API.
Flat Path : projects/{project}/zones/{zone}/vmExtensions
▼ ▲ compute.networks.updateNetworkProfile
Scopes :
Apiversion : 2026-10-01-preview
HTTP Method : POST
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
project
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])?))
Required : Yes
Type : string
Location : path
network
Required : Yes
Type : string
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?|[1-9][0-9]{0,19}
Location : path
Description : Name of the network resource to update the network profile for.
Description : Updates the network profile of the specified network. Currently only the following operations are supported: - Removing a Regionally Bound Network Profile
Flat Path : projects/{project}/global/networks/{network}/updateNetworkProfile
Path : projects/{project}/global/networks/{network}/updateNetworkProfile
Parameter Order :
▼ ▲ compute.regionSslCertificates.fetchEncryptionKey
Description : Returns the public encryption key used to encrypt the TLS private key before upload.
Parameter Order :
Flat Path : projects/{project}/regions/{region}/sslCertificates/encryptionKey
HTTP Method : GET
Parameters :
project
Location : path
Required : Yes
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])?))
region
Description : Name of the region scoping this request.
Type : string
Location : path
Required : Yes
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
Apiversion : 2026-10-01-preview
Path : projects/{project}/regions/{region}/sslCertificates/encryptionKey
Scopes :
▼ ▲ compute.organizationGlobalVmExtensionPolicies.delete
Apiversion : 2026-10-01-preview
Scopes :
HTTP Method : POST
Parameters :
globalVmExtensionPolicy
Type : string
Required : Yes
Description : Name of the global VM extension policy to purge scoped resources for.
Location : path
organization
Location : path
Type : string
Required : Yes
Description : Organization ID for this request.
Pattern : organizations/[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).
Location : query
Type : string
Path : {+organization}/global/vmExtensionPolicies/{globalVmExtensionPolicy}/delete
Parameter Order :
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.
Flat Path : organizations/{organizationsId}/global/vmExtensionPolicies/{globalVmExtensionPolicy}/delete
▼ ▲ compute.organizationGlobalVmExtensionPolicies.update
Description : Updates an organization level GlobalVmExtensionPolicy.
Path : {+organization}/global/vmExtensionPolicies/{globalVmExtensionPolicy}
Parameter Order :
Apiversion : 2026-10-01-preview
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).
Type : string
Location : query
globalVmExtensionPolicy
Type : string
Description : Name of the global VM extension policy to update.
Required : Yes
Location : path
organization
Pattern : organizations/[0-9]{0,20}
Required : Yes
Location : path
Description : Organization ID for this request.
Type : string
Flat Path : organizations/{organizationsId}/global/vmExtensionPolicies/{globalVmExtensionPolicy}
Scopes :
▼ ▲ compute.organizationGlobalVmExtensionPolicies.listVmExtensions
Apiversion : 2026-10-01-preview
Scopes :
Description : Lists all VM extensions within an organization. This is a read-only API.
Path : {+organization}/global/vmExtensions
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`)
Default : 500
Minimum : 0
Type : integer
Format : uint32
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
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
organization
Pattern : organizations/[0-9]{0,20}
Required : Yes
Location : path
Type : string
Description : Required. 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.
Location : query
Type : string
Parameter Order : organization
Flat Path : organizations/{organizationsId}/global/vmExtensions
▼ ▲ compute.organizationGlobalVmExtensionPolicies.get
Scopes :
Description : Gets details of an organization level GlobalVmExtensionPolicy.
Parameter Order :
HTTP Method : GET
Parameters :
globalVmExtensionPolicy
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 GlobalVmExtensionPolicy resource to return.
Type : string
organization
Description : Organization ID for this request.
Type : string
Location : path
Pattern : organizations/[0-9]{0,20}
Required : Yes
Path : {+organization}/global/vmExtensionPolicies/{globalVmExtensionPolicy}
Flat Path : organizations/{organizationsId}/global/vmExtensionPolicies/{globalVmExtensionPolicy}
Apiversion : 2026-10-01-preview
▼ ▲ compute.organizationGlobalVmExtensionPolicies.aggregatedList
Apiversion : 2026-10-01-preview
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`.
HTTP Method : GET
Parameters :
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.
organization
Description : Organization ID for this request.
Pattern : organizations/[0-9]{0,20}
Type : string
Location : path
Required : Yes
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
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
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
Format : uint32
Location : query
Type : integer
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`)
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
Path : {+organization}/aggregated/vmExtensionPolicies
Scopes :
Flat Path : organizations/{organizationsId}/aggregated/vmExtensionPolicies
▼ ▲ compute.organizationGlobalVmExtensionPolicies.insert
Flat Path : organizations/{organizationsId}/global/vmExtensionPolicies
Parameter Order : organization
Path : {+organization}/global/vmExtensionPolicies
HTTP Method : POST
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).
Type : string
Location : query
organization
Description : Organization ID for this request.
Type : string
Location : path
Pattern : organizations/[0-9]{0,20}
Required : Yes
Description : Creates a new organization level GlobalVmExtensionPolicy.
Apiversion : 2026-10-01-preview
Scopes :
▼ ▲ compute.organizationGlobalVmExtensionPolicies.list
Description : Lists organization level GlobalVmExtensionPolicies.
Flat Path : organizations/{organizationsId}/global/vmExtensionPolicies
Path : {+organization}/global/vmExtensionPolicies
Scopes :
Parameter Order : organization
HTTP Method : GET
Parameters :
organization
Description : Organization ID for this request.
Location : path
Required : Yes
Pattern : organizations/[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.
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
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
maxResults
Default : 500
Minimum : 0
Location : query
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`)
Apiversion : 2026-10-01-preview
▼ ▲ compute.organizationGlobalVmExtensionPolicies.getVmExtension
Flat Path : organizations/{organizationsId}/global/vmExtensions/{extensionName}
Path : {+organization}/global/vmExtensions/{extensionName}
Apiversion : 2026-10-01-preview
HTTP Method : GET
Parameters :
organization
Pattern : organizations/[0-9]{0,20}
Location : path
Description : Organization ID for this request.
Required : Yes
Type : string
extensionName
Required : Yes
Description : Required. Name of the VM extension for this request.
Type : string
Location : path
Scopes :
Description : Retrieves details of a specific VM extension.
Parameter Order :
▼ ▲ compute.sslCertificates.fetchEncryptionKey
Description : Returns the public encryption key used to encrypt the TLS private key before upload.
Parameter Order : project
Scopes :
Apiversion : 2026-10-01-preview
Flat Path : projects/{project}/global/sslCertificates/encryptionKey
Path : projects/{project}/global/sslCertificates/encryptionKey
HTTP Method : GET
Parameters :
project
Type : string
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])?))
Location : path
▼ ▲ compute.globalFolderOperations.get
Description : Retrieves the specified Operations resource.
Flat Path : folders/{foldersId}/global/operations/{operation}
Parameter Order :
Apiversion : 2026-10-01-preview
Path : {+folder}/global/operations/{operation}
Scopes :
HTTP Method : GET
Parameters :
operation
Required : Yes
Type : string
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?|[1-9][0-9]{0,19}
Location : path
Description : Name of the Operations resource to return.
folder
Pattern : folders/[0-9]{0,20}
Required : Yes
Description : Folder ID for this request.
Location : path
Type : string
▼ ▲ compute.globalFolderOperations.list
Path : {+folder}/global/operations
Apiversion : 2026-10-01-preview
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`)
Default : 500
Location : query
Type : integer
Format : uint32
Minimum : 0
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.
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.
folder
Pattern : folders/[0-9]{0,20}
Description : Folder ID for this request.
Required : Yes
Location : path
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
Description : Retrieves a list of Operation resources contained within the specified folder.
Parameter Order : folder
Scopes :
Flat Path : folders/{foldersId}/global/operations
▼ ▲ compute.folderZoneVmExtensionPolicies.insert
Description : Creates a new zone-level VM extension policy within a folder.
Scopes :
Flat Path : folders/{foldersId}/zones/{zone}/vmExtensionPolicies
Apiversion : 2026-10-01-preview
HTTP Method : POST
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).
Type : string
Location : query
folder
Description : Folder ID for this request.
Type : string
Required : Yes
Pattern : folders/[0-9]{0,20}
Location : path
zone
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
Required : Yes
Description : Name of the zone for this request.
Location : path
Type : string
Parameter Order :
Path : {+folder}/zones/{zone}/vmExtensionPolicies
▼ ▲ compute.folderZoneVmExtensionPolicies.list
Path : {+folder}/zones/{zone}/vmExtensionPolicies
Flat Path : folders/{foldersId}/zones/{zone}/vmExtensionPolicies
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
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`)
Default : 500
Minimum : 0
Type : integer
Location : query
Format : uint32
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.
folder
Type : string
Location : path
Pattern : folders/[0-9]{0,20}
Description : Folder ID for this request.
Required : Yes
zone
Location : path
Required : Yes
Type : string
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
Description : Name of the zone 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
Apiversion : 2026-10-01-preview
Parameter Order :
Description : Lists all VM extension policies within a specific zone for a folder.
Scopes :
▼ ▲ compute.folderZoneVmExtensionPolicies.update
Apiversion : 2026-10-01-preview
Description : Modifies an existing zone VM extension policy within a folder.
HTTP Method : PATCH
Parameters :
vmExtensionPolicy
Description : Name of the zone VM extension policy to update.
Location : path
Required : Yes
Type : string
folder
Pattern : folders/[0-9]{0,20}
Description : Folder ID for this request.
Location : path
Type : string
Required : Yes
zone
Required : Yes
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
Type : string
Location : path
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).
Parameter Order :
Flat Path : folders/{foldersId}/zones/{zone}/vmExtensionPolicies/{vmExtensionPolicy}
Path : {+folder}/zones/{zone}/vmExtensionPolicies/{vmExtensionPolicy}
Scopes :
▼ ▲ compute.folderZoneVmExtensionPolicies.getVmExtension
Flat Path : folders/{foldersId}/zones/{zone}/vmExtensions/{extensionName}
HTTP Method : GET
Parameters :
extensionName
Type : string
Location : path
Required : Yes
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?|[1-9][0-9]{0,19}
Description : Required. Name of the VM extension for this request.
zone
Description : Name of the zone for this request.
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
Type : string
Required : Yes
Location : path
folder
Pattern : folders/[0-9]{0,20}
Description : Folder ID for this request.
Type : string
Required : Yes
Location : path
Apiversion : 2026-10-01-preview
Parameter Order :
Description : Retrieves details of a specific VM extension within a folder.
Path : {+folder}/zones/{zone}/vmExtensions/{extensionName}
Scopes :
▼ ▲ compute.folderZoneVmExtensionPolicies.delete
Apiversion : 2026-10-01-preview
Parameter Order :
Flat Path : folders/{foldersId}/zones/{zone}/vmExtensionPolicies/{vmExtensionPolicy}
Path : {+folder}/zones/{zone}/vmExtensionPolicies/{vmExtensionPolicy}
HTTP Method : DELETE
Parameters :
folder
Description : Folder ID for this request.
Pattern : folders/[0-9]{0,20}
Required : Yes
Type : string
Location : path
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).
zone
Required : Yes
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
Type : string
Location : path
Description : Name of the zone for this request.
vmExtensionPolicy
Required : Yes
Type : string
Location : path
Description : Name of the zone VM extension policy to delete.
Scopes :
Description : Deletes a specified zone VM extension policy within a folder.
▼ ▲ compute.folderZoneVmExtensionPolicies.get
Parameter Order :
Path : {+folder}/zones/{zone}/vmExtensionPolicies/{vmExtensionPolicy}
Description : Retrieves details of a specific zone VM extension policy within a folder.
Apiversion : 2026-10-01-preview
HTTP Method : GET
Parameters :
zone
Description : Name of the zone for this request.
Location : path
Type : string
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
Required : Yes
folder
Location : path
Description : Folder ID for this request.
Required : Yes
Type : string
Pattern : folders/[0-9]{0,20}
vmExtensionPolicy
Type : string
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?|[1-9][0-9]{0,19}
Required : Yes
Location : path
Description : Name of the VM extension policy resource to return.
Scopes :
Flat Path : folders/{foldersId}/zones/{zone}/vmExtensionPolicies/{vmExtensionPolicy}
▼ ▲ compute.folderZoneVmExtensionPolicies.listVmExtensions
Scopes :
Flat Path : folders/{foldersId}/zones/{zone}/vmExtensions
Description : Lists all VM extensions within a specific zone for a folder. This is a read-only API.
Path : {+folder}/zones/{zone}/vmExtensions
HTTP Method : GET
Parameters :
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
folder
Required : Yes
Location : path
Type : string
Pattern : folders/[0-9]{0,20}
Description : Folder ID for this request.
zone
Required : Yes
Description : Name of the zone for this request.
Location : path
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
Type : string
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
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
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
Default : 500
Type : integer
Parameter Order :
Apiversion : 2026-10-01-preview
▼ ▲ compute.zoneFolderOperations.get
Description : Retrieves the specified Operations resource.
Parameter Order :
Path : {+folder}/zones/{zone}/operations/{operation}
Scopes :
Apiversion : 2026-10-01-preview
Flat Path : folders/{foldersId}/zones/{zone}/operations/{operation}
HTTP Method : GET
Parameters :
operation
Location : path
Required : Yes
Description : Name of the Operations resource to return.
Type : string
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?|[1-9][0-9]{0,19}
folder
Pattern : folders/[0-9]{0,20}
Type : string
Required : Yes
Location : path
Description : Folder ID for this request.
zone
Description : Name of the zone for this request.
Type : string
Location : path
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
Required : Yes
▼ ▲ compute.zoneFolderOperations.list
Parameter Order :
Description : Retrieves a list of Operation resources contained within the specified folder.
Flat Path : folders/{foldersId}/zones/{zone}/operations
Path : {+folder}/zones/{zone}/operations
HTTP Method : GET
Parameters :
zone
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
Required : Yes
Description : Name of the zone for request.
Location : path
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.
maxResults
Type : integer
Minimum : 0
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`)
Default : 500
Location : query
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.
folder
Pattern : folders/[0-9]{0,20}
Required : Yes
Location : path
Description : Folder ID for this request.
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
Scopes :
Apiversion : 2026-10-01-preview