2026-11-01
▼ ▲ compute.networkLocationBindings.list
Scopes :
Parameters :
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
Description : Specifies a page token to use. Set `pageToken` to the `nextPageToken` returned by a previous list request to get the next page of results.
Location : query
Type : string
project
Type : string
Pattern : (?:(?:[-a-z0-9]{1,63}\.)*(?:[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?):)?(?:[0-9]{1,19}|(?:[a-z0-9](?:[-a-z0-9]{0,61}[a-z0-9])?))
Description : Project ID for this request.
Location : path
Required : Yes
maxResults
Default : 500
Description : The maximum number of results per page that should be returned. If the number of available results is larger than `maxResults`, Compute Engine returns a `nextPageToken` that can be used to get the next page of results in subsequent list requests. Acceptable values are `0` to `500`, inclusive. (Default: `500`)
Type : integer
Location : query
Minimum : 0
Format : uint32
region
Type : string
Description : Name of the region of this request.
Location : path
Required : Yes
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
Description : Lists the NetworkLocationBindings for a project in the given scope.
Flat Path : projects/{project}/regions/{region}/networkLocationBindings
Path : projects/{project}/regions/{region}/networkLocationBindings
Parameter Order :
Apiversion : 2026-10-01-preview
HTTP Method : GET
▼ ▲ compute.networkLocationBindings.get
Path : projects/{project}/regions/{region}/networkLocationBindings/{networkLocationBinding}
Parameter Order :
Parameters :
region
Type : string
Location : path
Required : Yes
Description : Name of the region of this request.
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
networkLocationBinding
Description : Name of the NetworkLocationBinding resource to return.
Location : path
Required : Yes
Type : string
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?|[1-9][0-9]{0,19}
project
Type : string
Location : path
Required : Yes
Pattern : (?:(?:[-a-z0-9]{1,63}\.)*(?:[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?):)?(?:[0-9]{1,19}|(?:[a-z0-9](?:[-a-z0-9]{0,61}[a-z0-9])?))
Description : Project ID for this request.
Flat Path : projects/{project}/regions/{region}/networkLocationBindings/{networkLocationBinding}
Description : Returns the specified NetworkLocationBinding resource in the given scope.
Apiversion : 2026-10-01-preview
Scopes :
HTTP Method : GET
▼ ▲ compute.folderRolloutPlans.delete
Scopes :
Parameters :
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).
rolloutPlan
Type : string
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
Required : Yes
folder
Type : string
Description : Folder ID for this request.
Pattern : folders/[0-9]{0,20}
Location : path
Required : Yes
Description : Deletes a FolderRolloutPlan.
Path : {+folder}/global/rolloutPlans/{rolloutPlan}
Parameter Order :
Apiversion : 2026-10-01-preview
Flat Path : folders/{foldersId}/global/rolloutPlans/{rolloutPlan}
HTTP Method : DELETE
▼ ▲ compute.folderRolloutPlans.insert
Path : {+folder}/global/rolloutPlans
Flat Path : folders/{foldersId}/global/rolloutPlans
Parameters :
requestId
Description : An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments. The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000).
Location : query
Type : string
folder
Type : string
Location : path
Required : Yes
Pattern : folders/[0-9]{0,20}
Description : Folder ID for this request.
Apiversion : 2026-10-01-preview
Scopes :
HTTP Method : POST
Parameter Order : folder
Description : Creates a new RolloutPlan in a given folder and location.
▼ ▲ compute.folderRolloutPlans.list
Scopes :
HTTP Method : GET
Description : Lists FolderRolloutPlans in a given folder and location.
Apiversion : 2026-10-01-preview
Parameter Order : folder
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.
Type : string
Location : query
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
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.
folder
Type : string
Description : Folder ID for this request.
Location : path
Required : Yes
Pattern : folders/[0-9]{0,20}
maxResults
Description : The maximum number of results per page that should be returned. If the number of available results is larger than `maxResults`, Compute Engine returns a `nextPageToken` that can be used to get the next page of results in subsequent list requests. Acceptable values are `0` to `500`, inclusive. (Default: `500`)
Minimum : 0
Location : query
Format : uint32
Default : 500
Type : integer
Path : {+folder}/global/rolloutPlans
Flat Path : folders/{foldersId}/global/rolloutPlans
▼ ▲ compute.folderRolloutPlans.get
Description : Gets details of a single folder-scoped RolloutPlan.
HTTP Method : GET
Parameter Order :
Scopes :
Path : {+folder}/global/rolloutPlans/{rolloutPlan}
Apiversion : 2026-10-01-preview
Parameters :
folder
Description : Folder ID for this request.
Type : string
Pattern : folders/[0-9]{0,20}
Location : path
Required : Yes
rolloutPlan
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 persistent rollout plan to return.
Flat Path : folders/{foldersId}/global/rolloutPlans/{rolloutPlan}
▼ ▲ compute.folderRollouts.delete
Parameters :
rollout
Location : path
Required : Yes
Description : Name of the Rollout resource to delete.
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?|[1-9][0-9]{0,19}
Type : string
requestId
Description : An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments. The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000).
Type : string
Location : query
folder
Location : path
Required : Yes
Type : string
Pattern : folders/[0-9]{1,19}
Description : Required. Folder ID for this request.
Parameter Order :
Scopes :
HTTP Method : DELETE
Path : {+folder}/global/rollouts/{rollout}
Flat Path : folders/{foldersId}/global/rollouts/{rollout}
Description : Deletes a Rollout.
Apiversion : 2026-10-01-preview
▼ ▲ compute.folderRollouts.resume
Scopes :
Apiversion : 2026-10-01-preview
HTTP Method : POST
Flat Path : folders/{foldersId}/global/rollouts/{rollout}/resume
Description : Resumes a Rollout.
Path : {+folder}/global/rollouts/{rollout}/resume
Parameters :
folder
Description : Required. Folder ID for this request.
Type : string
Pattern : folders/[0-9]{1,19}
Location : path
Required : Yes
etag
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.
Type : string
rollout
Description : Required. Name of the Rollout resource to resume.
Location : path
Required : Yes
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?|[1-9][0-9]{0,19}
Type : string
requestId
Description : An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments. The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000).
Location : query
Type : string
Parameter Order :
▼ ▲ compute.folderRollouts.advance
Parameters :
folder
Type : string
Description : Required. Folder ID for this request.
Pattern : folders/[0-9]{1,19}
Location : path
Required : Yes
currentWaveNumber
Format : int64
Description : Required. Wave number of the current wave.
Type : string
Location : query
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
rollout
Type : string
Location : path
Required : Yes
Description : Required. Name of the Rollout resource to advance.
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?|[1-9][0-9]{0,19}
Parameter Order :
Flat Path : folders/{foldersId}/global/rollouts/{rollout}/advance
Scopes :
Description : Advances a Rollout to the next wave, or completes it if no waves remain.
Path : {+folder}/global/rollouts/{rollout}/advance
HTTP Method : POST
Apiversion : 2026-10-01-preview
▼ ▲ compute.folderRollouts.list
HTTP Method : GET
Apiversion : 2026-10-01-preview
Flat Path : folders/{foldersId}/global/rollouts
Path : {+folder}/global/rollouts
Parameter Order : folder
Parameters :
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.
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
maxResults
Default : 500
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`)
Location : query
Minimum : 0
folder
Description : Required. Folder ID for this request.
Pattern : folders/[0-9]{1,19}
Type : string
Location : path
Required : Yes
Description : Lists Rollouts in a given folder and location.
Scopes :
▼ ▲ compute.folderRollouts.get
HTTP Method : GET
Scopes :
Apiversion : 2026-10-01-preview
Parameter Order :
Parameters :
folder
Description : Folder ID for this request.
Type : string
Pattern : folders/[0-9]{0,20}
Location : path
Required : Yes
rollout
Type : string
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?|[1-9][0-9]{0,19}
Description : Name of the persistent rollout to return.
Location : path
Required : Yes
Description : Gets details of a single folder-scoped Rollout.
Path : {+folder}/global/rollouts/{rollout}
Flat Path : folders/{foldersId}/global/rollouts/{rollout}
▼ ▲ compute.folderRollouts.cancel
HTTP Method : PATCH
Parameter Order :
Apiversion : 2026-10-01-preview
Flat Path : folders/{foldersId}/global/rollouts/{rollout}
Parameters :
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).
rollout
Description : Name of the Rollout resource to cancel.
Type : string
Location : path
Required : Yes
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?|[1-9][0-9]{0,19}
folder
Pattern : folders/[0-9]{1,19}
Description : Required. Folder ID for this request.
Type : string
Location : path
Required : Yes
rollback
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
Location : query
Scopes :
Path : {+folder}/global/rollouts/{rollout}
Description : Cancels a Rollout.
▼ ▲ compute.folderRollouts.pause
Scopes :
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
rollout
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?|[1-9][0-9]{0,19}
Type : string
Location : path
Required : Yes
Description : Required. Name of the Rollout resource to pause.
etag
Type : string
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
folder
Location : path
Required : Yes
Description : Required. Folder ID for this request.
Pattern : folders/[0-9]{1,19}
Type : string
Path : {+folder}/global/rollouts/{rollout}/pause
Description : Pauses a Rollout.
Flat Path : folders/{foldersId}/global/rollouts/{rollout}/pause
Parameter Order :
Apiversion : 2026-10-01-preview
HTTP Method : POST
▼ ▲ compute.sslCertificates.fetchEncryptionKey
Parameters :
name
Location : query
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
Type : string
Description : Required. Name of the SslCertificate resource to be created. The name must be 1-63 characters long, and comply withRFC1035.
▼ ▲ compute.regionSslCertificates.fetchEncryptionKey
Parameters :
name
Location : query
Type : string
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
Description : Required. Name of the SslCertificate resource to be created. The name must be 1-63 characters long, and comply withRFC1035.