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