2026-11-10
▼ ▲ compute.organizationSnapshotRecycleBinPolicy.get
Parameter Order : organization
Scopes :
Path : {+organization}/global/snapshotRecycleBinPolicy
Apiversion : 2026-12-01-preview
Description : Returns the specified SnapshotRecycleBinPolicy.
Parameters :
organization
Location : path
Required : Yes
Description : Organization ID for this request.
Type : string
Pattern : organizations/[0-9]{0,20}
Flat Path : organizations/{organizationsId}/global/snapshotRecycleBinPolicy
HTTP Method : GET
▼ ▲ compute.organizationSnapshotRecycleBinPolicy.patch
Apiversion : 2026-12-01-preview
Flat Path : organizations/{organizationsId}/global/snapshotRecycleBinPolicy
Scopes :
HTTP Method : PATCH
Path : {+organization}/global/snapshotRecycleBinPolicy
Parameter Order : organization
Description : Patches the SnapshotRecycleBinPolicy.
Parameters :
organization
Type : string
Pattern : organizations/[0-9]{0,20}
Location : path
Required : Yes
Description : Organization ID for this request.
requestId
Description : An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments. The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000).
Type : string
Location : query
▼ ▲ compute.networkLocationBindings.list
Scopes :
Flat Path : projects/{project}/regions/{region}/networkLocationBindings
Description : Lists the NetworkLocationBindings for a project in the given scope.
Path : projects/{project}/regions/{region}/networkLocationBindings
Parameter Order :
Apiversion : 2026-12-01-preview
Parameters :
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.
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
maxResults
Type : integer
Description : The maximum number of results per page that should be returned. If the number of available results is larger than `maxResults`, Compute Engine returns a `nextPageToken` that can be used to get the next page of results in subsequent list requests. Acceptable values are `0` to `500`, inclusive. (Default: `500`)
Minimum : 0
Default : 500
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
region
Type : string
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
Description : Name of the region of this request.
Location : path
Required : Yes
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
HTTP Method : GET
▼ ▲ compute.networkLocationBindings.get
Parameter Order :
Path : projects/{project}/regions/{region}/networkLocationBindings/{networkLocationBinding}
Apiversion : 2026-12-01-preview
Description : Returns the specified NetworkLocationBinding resource in the given scope.
Flat Path : projects/{project}/regions/{region}/networkLocationBindings/{networkLocationBinding}
HTTP Method : GET
Scopes :
Parameters :
region
Location : path
Required : Yes
Type : string
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
Description : Name of the region of this request.
networkLocationBinding
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?|[1-9][0-9]{0,19}
Location : path
Required : Yes
Description : Name of the NetworkLocationBinding resource to return.
Type : string
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.
▼ ▲ compute.networks.updateNetworkProfile
HTTP Method : POST
Scopes :
Description : Updates the network profile of the specified network. Currently only the following operations are supported: - Removing a Regionally Bound Network Profile
Path : projects/{project}/global/networks/{network}/updateNetworkProfile
Parameters :
project
Description : Project ID for this request.
Type : string
Pattern : (?:(?:[-a-z0-9]{1,63}\.)*(?:[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?):)?(?:[0-9]{1,19}|(?:[a-z0-9](?:[-a-z0-9]{0,61}[a-z0-9])?))
Location : path
Required : Yes
network
Type : string
Description : Name of the network resource to update the network profile for.
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?|[1-9][0-9]{0,19}
Location : path
Required : Yes
requestId
Type : string
Location : query
Description : An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments. The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000).
Apiversion : 2026-12-01-preview
Flat Path : projects/{project}/global/networks/{network}/updateNetworkProfile
Parameter Order :
▼ ▲ compute.snapshots.getEffectiveRecycleBinRule
Path : projects/{project}/global/snapshots/{snapshot}/getEffectiveRecycleBinRule
Flat Path : projects/{project}/global/snapshots/{snapshot}/getEffectiveRecycleBinRule
Apiversion : 2026-12-01-preview
Description : Returns the effective recycle bin rule for a snapshot by merging org and project level rules. If no rules are defined at org and project level, the standard default rule is returned.
Parameters :
snapshot
Type : string
Location : path
Required : Yes
Description : Name of the Snapshot resource to get the effective recycle bin rule for.
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?|[1-9][0-9]{0,19}
project
Description : Project ID for this request.
Location : path
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])?))
Scopes :
HTTP Method : GET
Parameter Order :
▼ ▲ compute.snapshotRecycleBinPolicy.patch
Flat Path : projects/{project}/global/snapshotRecycleBinPolicy
Description : Patches the SnapshotRecycleBinPolicy.
Apiversion : 2026-12-01-preview
Path : projects/{project}/global/snapshotRecycleBinPolicy
Scopes :
Parameters :
project
Location : path
Required : Yes
Type : string
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])?))
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
Parameter Order : project
HTTP Method : PATCH
▼ ▲ compute.snapshotRecycleBinPolicy.get
Parameter Order : project
Apiversion : 2026-12-01-preview
Flat Path : projects/{project}/global/snapshotRecycleBinPolicy
Scopes :
Parameters :
project
Type : string
Description : Project ID for this request.
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 : Returns the specified SnapshotRecycleBinPolicy.
HTTP Method : GET
Path : projects/{project}/global/snapshotRecycleBinPolicy
▼ ▲ compute.recoverableSnapshots.setIamPolicy
Scopes :
Flat Path : projects/{project}/global/recoverableSnapshots/{resource}/setIamPolicy
Apiversion : 2026-12-01-preview
HTTP Method : POST
Path : projects/{project}/global/recoverableSnapshots/{resource}/setIamPolicy
Description : Sets the access control policy on the specified resource. Replaces any existing policy.
Parameter Order :
Parameters :
resource
Location : path
Required : Yes
Pattern : [a-z](?:[-a-z0-9_]{0,61}[a-z0-9])?|[1-9][0-9]{0,19}
Description : Name or id of the resource for this request.
Type : string
project
Location : path
Required : Yes
Description : Project ID for this request.
Pattern : (?:(?:[-a-z0-9]{1,63}\.)*(?:[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?):)?(?:[0-9]{1,19}|(?:[a-z0-9](?:[-a-z0-9]{0,61}[a-z0-9])?))
Type : string
▼ ▲ compute.recoverableSnapshots.delete
Parameter Order :
Path : projects/{project}/global/recoverableSnapshots/{recoverableSnapshot}
Flat Path : projects/{project}/global/recoverableSnapshots/{recoverableSnapshot}
Apiversion : 2026-12-01-preview
Scopes :
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.
recoverableSnapshot
Type : string
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?|[1-9][0-9]{0,19}
Description : Name of the recoverable Snapshot resource to delete.
Location : path
Required : Yes
requestId
Description : An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments. The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000).
Type : string
Location : query
Description : Deletes the specified RecoverableSnapshot. Deleting a recoverable snapshot will delete the underlying PD snapshot and is irreversible.
HTTP Method : DELETE
▼ ▲ compute.recoverableSnapshots.testIamPermissions
Parameter Order :
HTTP Method : POST
Description : Returns permissions that a caller has on the specified resource.
Flat Path : projects/{project}/global/recoverableSnapshots/{resource}/testIamPermissions
Parameters :
resource
Type : string
Location : path
Required : Yes
Pattern : [a-z](?:[-a-z0-9_]{0,61}[a-z0-9])?|[1-9][0-9]{0,19}
Description : Name or id of the resource for this request.
project
Location : path
Required : Yes
Type : string
Pattern : (?:(?:[-a-z0-9]{1,63}\.)*(?:[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?):)?(?:[0-9]{1,19}|(?:[a-z0-9](?:[-a-z0-9]{0,61}[a-z0-9])?))
Description : Project ID for this request.
Scopes :
Path : projects/{project}/global/recoverableSnapshots/{resource}/testIamPermissions
Apiversion : 2026-12-01-preview
▼ ▲ compute.recoverableSnapshots.getIamPolicy
Description : Gets the access control policy for a resource. May be empty if no such policy or resource exists.
Apiversion : 2026-12-01-preview
Path : projects/{project}/global/recoverableSnapshots/{resource}/getIamPolicy
HTTP Method : GET
Flat Path : projects/{project}/global/recoverableSnapshots/{resource}/getIamPolicy
Parameters :
optionsRequestedPolicyVersion
Description : Requested IAM Policy version.
Format : int32
Location : query
Type : integer
project
Type : string
Pattern : (?:(?:[-a-z0-9]{1,63}\.)*(?:[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?):)?(?:[0-9]{1,19}|(?:[a-z0-9](?:[-a-z0-9]{0,61}[a-z0-9])?))
Location : path
Required : Yes
Description : Project ID for this request.
resource
Location : path
Required : Yes
Pattern : [a-z](?:[-a-z0-9_]{0,61}[a-z0-9])?|[1-9][0-9]{0,19}
Type : string
Description : Name or id of the resource for this request.
Scopes :
Parameter Order :
▼ ▲ compute.recoverableSnapshots.list
Scopes :
Flat Path : projects/{project}/global/recoverableSnapshots
Description : Retrieves a list of all of the RecoverableSnapshots in your project.
Apiversion : 2026-12-01-preview
Path : projects/{project}/global/recoverableSnapshots
Parameters :
orderBy
Type : string
Description : Sorts list results by a certain order. By default, results are returned in alphanumerical order based on the resource name. You can also sort results in descending order based on the creation timestamp using `orderBy="creationTimestamp desc"`. This sorts results based on the `creationTimestamp` field in reverse chronological order (newest result first). Use this to sort resources like operations so that the newest operation is returned first. Currently, only sorting by `name` or `creationTimestamp desc` is supported.
Location : query
project
Description : Project ID for this request.
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
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
maxResults
Location : query
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`)
Format : uint32
Type : integer
Minimum : 0
filter
Location : query
Description : A filter expression that filters resources listed in the response. Most Compute resources support two types of filter expressions: expressions that support regular expressions and expressions that follow API improvement proposal AIP-160. These two types of filter expressions cannot be mixed in one request. If you want to use AIP-160, your expression must specify the field name, an operator, and the value that you want to use for filtering. The value must be a string, a number, or a boolean. The operator must be either `=`, `!=`, `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute Engine instances, you can exclude instances named `example-instance` by specifying `name != example-instance`. The `:*` comparison can be used to test whether a key has been defined. For example, to find all objects with `owner` label use: ``` labels.owner:* ``` You can also filter nested fields. For example, you could specify `scheduling.automaticRestart = false` to include instances only if they are not scheduled for automatic restarts. You can use filtering on nested fields to filter based onresource labels. To filter on multiple expressions, provide each separate expression within parentheses. For example: ``` (scheduling.automaticRestart = true) (cpuPlatform = "Intel Skylake") ``` By default, each expression is an `AND` expression. However, you can include `AND` and `OR` expressions explicitly. For example: ``` (cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.automaticRestart = true) ``` If you want to use a regular expression, use the `eq` (equal) or `ne` (not equal) operator against a single un-parenthesized expression with or without quotes or against multiple parenthesized expressions. Examples: `fieldname eq unquoted literal` `fieldname eq 'single quoted literal'` `fieldname eq "double quoted literal"` `(fieldname1 eq literal) (fieldname2 ne "literal")` The literal value is interpreted as a regular expression using GoogleRE2 library syntax. The literal value must match the entire field. For example, to filter for instances that do not end with name "instance", you would use `name ne .*instance`. You cannot combine constraints on multiple fields using regular expressions.
Type : string
Parameter Order : project
HTTP Method : GET
▼ ▲ compute.recoverableSnapshots.get
Description : Returns the specified RecoverableSnapshot resource.
Apiversion : 2026-12-01-preview
Scopes :
Flat Path : projects/{project}/global/recoverableSnapshots/{recoverableSnapshot}
Parameter Order :
Parameters :
project
Description : Project ID for this request.
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
recoverableSnapshot
Location : path
Required : Yes
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?|[1-9][0-9]{0,19}
Type : string
Description : Name of the Snapshot resource to return.
Path : projects/{project}/global/recoverableSnapshots/{recoverableSnapshot}
HTTP Method : GET
▼ ▲ compute.recoverableSnapshots.recover
Flat Path : projects/{project}/global/recoverableSnapshots/{recoverableSnapshot}/recover
Description : Recovers the specified RecoverableSnapshot.
Parameters :
project
Description : Project Id of the request
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
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
snapshotName
Description : Optional. Name of the snapshot after the recovery The name will be 1-63 characters long, and comply withRFC1035. Specifically, the name will be 1-63 characters long and match the regular expression `[a-z]([-a-z0-9]*[a-z0-9])?` which means the first character will be a lowercase letter, and all following characters can be a dash, lowercase letter, or digit, except the last character, which cannot be a dash.
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?
Location : query
Type : string
recoverableSnapshot
Description : Name of the recoverable resource to recover
Type : string
Pattern : [a-z](?:[-a-z0-9]{0,61}[a-z0-9])?|[1-9][0-9]{0,19}
Location : path
Required : Yes
Parameter Order :
HTTP Method : POST
Path : projects/{project}/global/recoverableSnapshots/{recoverableSnapshot}/recover
Scopes :
Apiversion : 2026-12-01-preview