- HTTP request
- Path parameters
- Query parameters
- Request body
- Response body
- Authorization Scopes
- IAM Permissions
- Try it!
Deletes the specified network endpoint group.Note that the NEG cannot be deleted if there are backend services referencing it.
The URL uses gRPC Transcoding syntax.
Project ID for this request.
The name of the network endpoint group to delete. It should comply with RFC1035.
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 (
The request body must be empty.
If successful, the response body contains data with the following structure:
Represents an Operation resource.
Google Compute Engine has three Operation resources:
You can use an operation resource to manage asynchronous API requests. For more information, read Handling API responses.
Operations can be global, regional or zonal.
- For global operations, use the
- For regional operations, use the
- For zonal operations, use the
For more information, read Global, Regional, and Zonal Resources.