2026-11-03
▼ ▲ compute.networkLocationBindings.get
Parameter Order :
Parameters :
project
Required : Yes
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])?))
Description : Project ID for this request.
networkLocationBinding
Required : Yes
Type : string
Location : path
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?|[1-9][0-9]{0,19}
Description : Name of the NetworkLocationBinding resource to return.
region
Location : path
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
Required : Yes
Description : Name of the region of this request.
Type : string
Flat Path : projects/{project}/regions/{region}/networkLocationBindings/{networkLocationBinding}
Description : Returns the specified NetworkLocationBinding resource in the given scope.
Scopes :
Apiversion : 2026-10-01-preview
HTTP Method : GET
Path : projects/{project}/regions/{region}/networkLocationBindings/{networkLocationBinding}
▼ ▲ compute.networkLocationBindings.list
Scopes :
Flat Path : projects/{project}/regions/{region}/networkLocationBindings
Parameter Order :
Description : Lists the NetworkLocationBindings for a project in the given scope.
Apiversion : 2026-10-01-preview
HTTP Method : GET
Parameters :
region
Required : Yes
Type : string
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
Description : Name of the region of this request.
Location : path
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
pageToken
Type : string
Location : query
Description : Specifies a page token to use. Set `pageToken` to the `nextPageToken` returned by a previous list request to get the next page of results.
filter
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
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
Format : uint32
Default : 500
orderBy
Type : string
Location : query
Description : Sorts list results by a certain order. By default, results are returned in alphanumerical order based on the resource name. You can also sort results in descending order based on the creation timestamp using `orderBy="creationTimestamp desc"`. This sorts results based on the `creationTimestamp` field in reverse chronological order (newest result first). Use this to sort resources like operations so that the newest operation is returned first. Currently, only sorting by `name` or `creationTimestamp desc` is supported.
Path : projects/{project}/regions/{region}/networkLocationBindings
▼ ▲ compute.folderRollouts.advance
Description : Advances a Rollout to the next wave, or completes it if no waves remain.
Flat Path : folders/{foldersId}/global/rollouts/{rollout}/advance
Apiversion : 2026-10-01-preview
HTTP Method : POST
Parameters :
currentWaveNumber
Format : int64
Description : Required. Wave number of the current wave.
Location : query
Type : string
folder
Location : path
Description : Required. Folder ID for this request.
Pattern : folders/[0-9]{1,19}
Type : string
Required : Yes
requestId
Description : An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments. The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000).
Location : query
Type : string
rollout
Description : Required. Name of the Rollout resource to advance.
Required : Yes
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?|[1-9][0-9]{0,19}
Type : string
Location : path
Scopes :
Parameter Order :
Path : {+folder}/global/rollouts/{rollout}/advance
▼ ▲ compute.folderRollouts.list
Apiversion : 2026-10-01-preview
HTTP Method : GET
Scopes :
Description : Lists Rollouts in a given folder and location.
Parameters :
maxResults
Minimum : 0
Location : query
Format : uint32
Type : integer
Description : The maximum number of results per page that should be returned. If the number of available results is larger than `maxResults`, Compute Engine returns a `nextPageToken` that can be used to get the next page of results in subsequent list requests. Acceptable values are `0` to `500`, inclusive. (Default: `500`)
Default : 500
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
Location : query
Description : Specifies a page token to use. Set `pageToken` to the `nextPageToken` returned by a previous list request to get the next page of results.
Type : string
filter
Location : query
Type : string
Description : A filter expression that filters resources listed in the response. Most Compute resources support two types of filter expressions: expressions that support regular expressions and expressions that follow API improvement proposal AIP-160. These two types of filter expressions cannot be mixed in one request. If you want to use AIP-160, your expression must specify the field name, an operator, and the value that you want to use for filtering. The value must be a string, a number, or a boolean. The operator must be either `=`, `!=`, `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute Engine instances, you can exclude instances named `example-instance` by specifying `name != example-instance`. The `:*` comparison can be used to test whether a key has been defined. For example, to find all objects with `owner` label use: ``` labels.owner:* ``` You can also filter nested fields. For example, you could specify `scheduling.automaticRestart = false` to include instances only if they are not scheduled for automatic restarts. You can use filtering on nested fields to filter based onresource labels. To filter on multiple expressions, provide each separate expression within parentheses. For example: ``` (scheduling.automaticRestart = true) (cpuPlatform = "Intel Skylake") ``` By default, each expression is an `AND` expression. However, you can include `AND` and `OR` expressions explicitly. For example: ``` (cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.automaticRestart = true) ``` If you want to use a regular expression, use the `eq` (equal) or `ne` (not equal) operator against a single un-parenthesized expression with or without quotes or against multiple parenthesized expressions. Examples: `fieldname eq unquoted literal` `fieldname eq 'single quoted literal'` `fieldname eq "double quoted literal"` `(fieldname1 eq literal) (fieldname2 ne "literal")` The literal value is interpreted as a regular expression using GoogleRE2 library syntax. The literal value must match the entire field. For example, to filter for instances that do not end with name "instance", you would use `name ne .*instance`. You cannot combine constraints on multiple fields using regular expressions.
folder
Required : Yes
Location : path
Pattern : folders/[0-9]{1,19}
Type : string
Description : Required. Folder ID for this request.
Parameter Order : folder
Path : {+folder}/global/rollouts
Flat Path : folders/{foldersId}/global/rollouts
▼ ▲ compute.folderRollouts.cancel
Path : {+folder}/global/rollouts/{rollout}
Parameters :
folder
Type : string
Pattern : folders/[0-9]{1,19}
Location : path
Required : Yes
Description : Required. Folder ID for this request.
rollback
Location : query
Description : Optional. If true, then the ongoing rollout must be rolled back. Else, just cancel the rollout without taking any further actions. Note that products must support at least one of these options, however, it does not need to support both.
Type : boolean
rollout
Required : Yes
Description : Name of the Rollout resource to cancel.
Location : path
Type : string
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?|[1-9][0-9]{0,19}
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).
Parameter Order :
Scopes :
Description : Cancels a Rollout.
Apiversion : 2026-10-01-preview
HTTP Method : PATCH
Flat Path : folders/{foldersId}/global/rollouts/{rollout}
▼ ▲ compute.folderRollouts.delete
Scopes :
Path : {+folder}/global/rollouts/{rollout}
Parameter Order :
Apiversion : 2026-10-01-preview
HTTP Method : DELETE
Description : Deletes a Rollout.
Parameters :
folder
Type : string
Required : Yes
Description : Required. Folder ID for this request.
Location : path
Pattern : folders/[0-9]{1,19}
rollout
Type : string
Description : Name of the Rollout resource to delete.
Required : Yes
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?|[1-9][0-9]{0,19}
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).
Flat Path : folders/{foldersId}/global/rollouts/{rollout}
▼ ▲ compute.folderRollouts.pause
Parameters :
etag
Description : The etag of the Rollout. If this is provided, the request will only succeed if the etag matches the current etag of the Rollout.
Location : query
Type : string
folder
Pattern : folders/[0-9]{1,19}
Type : string
Description : Required. Folder ID for this request.
Required : Yes
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).
Type : string
Location : query
rollout
Type : string
Location : path
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?|[1-9][0-9]{0,19}
Required : Yes
Description : Required. Name of the Rollout resource to pause.
Flat Path : folders/{foldersId}/global/rollouts/{rollout}/pause
Path : {+folder}/global/rollouts/{rollout}/pause
Scopes :
Parameter Order :
Description : Pauses a Rollout.
Apiversion : 2026-10-01-preview
HTTP Method : POST
▼ ▲ compute.folderRollouts.get
Parameters :
folder
Pattern : folders/[0-9]{0,20}
Description : Folder ID for this request.
Type : string
Location : path
Required : Yes
rollout
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 persistent rollout to return.
Required : Yes
Description : Gets details of a single folder-scoped Rollout.
Flat Path : folders/{foldersId}/global/rollouts/{rollout}
Path : {+folder}/global/rollouts/{rollout}
Parameter Order :
Apiversion : 2026-10-01-preview
HTTP Method : GET
Scopes :
▼ ▲ compute.folderRollouts.resume
Scopes :
Path : {+folder}/global/rollouts/{rollout}/resume
Parameters :
requestId
Location : query
Description : An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments. The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000).
Type : string
folder
Location : path
Required : Yes
Description : Required. Folder ID for this request.
Pattern : folders/[0-9]{1,19}
Type : string
etag
Type : string
Location : query
Description : The etag of the Rollout. If this is provided, the request will only succeed if the etag matches the current etag of the Rollout.
rollout
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?|[1-9][0-9]{0,19}
Description : Required. Name of the Rollout resource to resume.
Location : path
Type : string
Required : Yes
Parameter Order :
Description : Resumes a Rollout.
Flat Path : folders/{foldersId}/global/rollouts/{rollout}/resume
Apiversion : 2026-10-01-preview
HTTP Method : POST
▼ ▲ compute.folderRolloutPlans.get
Parameter Order :
Description : Gets details of a single folder-scoped RolloutPlan.
Apiversion : 2026-10-01-preview
HTTP Method : GET
Path : {+folder}/global/rolloutPlans/{rolloutPlan}
Parameters :
folder
Description : Folder ID for this request.
Required : Yes
Pattern : folders/[0-9]{0,20}
Type : string
Location : path
rolloutPlan
Required : Yes
Location : path
Type : string
Description : Name of the persistent rollout plan to return.
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?|[1-9][0-9]{0,19}
Scopes :
Flat Path : folders/{foldersId}/global/rolloutPlans/{rolloutPlan}
▼ ▲ compute.folderRolloutPlans.list
Parameter Order : folder
Apiversion : 2026-10-01-preview
HTTP Method : GET
Description : Lists FolderRolloutPlans in a given folder and location.
Scopes :
Flat Path : folders/{foldersId}/global/rolloutPlans
Path : {+folder}/global/rolloutPlans
Parameters :
filter
Location : query
Description : A filter expression that filters resources listed in the response. Most Compute resources support two types of filter expressions: expressions that support regular expressions and expressions that follow API improvement proposal AIP-160. These two types of filter expressions cannot be mixed in one request. If you want to use AIP-160, your expression must specify the field name, an operator, and the value that you want to use for filtering. The value must be a string, a number, or a boolean. The operator must be either `=`, `!=`, `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute Engine instances, you can exclude instances named `example-instance` by specifying `name != example-instance`. The `:*` comparison can be used to test whether a key has been defined. For example, to find all objects with `owner` label use: ``` labels.owner:* ``` You can also filter nested fields. For example, you could specify `scheduling.automaticRestart = false` to include instances only if they are not scheduled for automatic restarts. You can use filtering on nested fields to filter based onresource labels. To filter on multiple expressions, provide each separate expression within parentheses. For example: ``` (scheduling.automaticRestart = true) (cpuPlatform = "Intel Skylake") ``` By default, each expression is an `AND` expression. However, you can include `AND` and `OR` expressions explicitly. For example: ``` (cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.automaticRestart = true) ``` If you want to use a regular expression, use the `eq` (equal) or `ne` (not equal) operator against a single un-parenthesized expression with or without quotes or against multiple parenthesized expressions. Examples: `fieldname eq unquoted literal` `fieldname eq 'single quoted literal'` `fieldname eq "double quoted literal"` `(fieldname1 eq literal) (fieldname2 ne "literal")` The literal value is interpreted as a regular expression using GoogleRE2 library syntax. The literal value must match the entire field. For example, to filter for instances that do not end with name "instance", you would use `name ne .*instance`. You cannot combine constraints on multiple fields using regular expressions.
Type : string
folder
Type : string
Required : Yes
Pattern : folders/[0-9]{0,20}
Description : Folder ID for this request.
Location : path
maxResults
Location : query
Format : uint32
Minimum : 0
Default : 500
Description : The maximum number of results per page that should be returned. If the number of available results is larger than `maxResults`, Compute Engine returns a `nextPageToken` that can be used to get the next page of results in subsequent list requests. Acceptable values are `0` to `500`, inclusive. (Default: `500`)
Type : integer
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.
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.
▼ ▲ compute.folderRolloutPlans.insert
Parameters :
folder
Type : string
Description : Folder ID for this request.
Required : Yes
Pattern : folders/[0-9]{0,20}
Location : path
requestId
Type : string
Description : An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments. The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000).
Location : query
Flat Path : folders/{foldersId}/global/rolloutPlans
Path : {+folder}/global/rolloutPlans
Parameter Order : folder
Apiversion : 2026-10-01-preview
HTTP Method : POST
Description : Creates a new RolloutPlan in a given folder and location.
Scopes :
▼ ▲ compute.folderRolloutPlans.delete
Scopes :
Apiversion : 2026-10-01-preview
HTTP Method : DELETE
Description : Deletes a FolderRolloutPlan.
Parameter Order :
Flat Path : folders/{foldersId}/global/rolloutPlans/{rolloutPlan}
Parameters :
folder
Description : Folder ID for this request.
Pattern : folders/[0-9]{0,20}
Required : Yes
Type : string
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
rolloutPlan
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?|[1-9][0-9]{0,19}
Description : Name of the FolderRolloutPlan resource to delete.
Location : path
Type : string
Required : Yes
Path : {+folder}/global/rolloutPlans/{rolloutPlan}
▼ ▲ compute.regionSslCertificates.fetchEncryptionKey
Parameters :
name
Description : Required. Name of the SslCertificate resource to be created. The name must be 1-63 characters long, and comply withRFC1035.
Location : query
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
Type : string
▼ ▲ compute.sslCertificates.fetchEncryptionKey
Parameters :
name
Type : string
Description : Required. Name of the SslCertificate resource to be created. The name must be 1-63 characters long, and comply withRFC1035.
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
Location : query