All Products
Document Center

Server Load Balancer:DeleteRules

Last Updated:Mar 01, 2024

Deletes one or more forwarding rules from a listener at a time.

Operation description

DeleteRules is an asynchronous operation. After a request is sent, the system returns a request ID and runs the task in the background. You can call the ListRules operation to query the status of forwarding rules.

  • If the forwarding rules are in the Deleting state, the forwarding rules are being deleted.
  • If the forwarding rules cannot be found, the forwarding rules are deleted.


OpenAPI Explorer automatically calculates the signature value. For your convenience, we recommend that you call this operation in OpenAPI Explorer.

Authorization information

The following table shows the authorization information corresponding to the API. The authorization information can be used in the Action policy element to grant a RAM user or RAM role the permissions to call this API operation. Description:

  • Operation: the value that you can use in the Action element to specify the operation on a resource.
  • Access level: the access level of each operation. The levels are read, write, and list.
  • Resource type: the type of the resource on which you can authorize the RAM user or the RAM role to perform the operation. Take note of the following items:
    • The required resource types are displayed in bold characters.
    • If the permissions cannot be granted at the resource level, All Resources is used in the Resource type column of the operation.
  • Condition Key: the condition key that is defined by the cloud service.
  • Associated operation: other operations that the RAM user or the RAM role must have permissions to perform to complete the operation. To complete the operation, the RAM user or the RAM role must have the permissions to perform the associated operations.
OperationAccess levelResource typeCondition keyAssociated operation
  • LoadBalancer

Request parameters


The client token that is used to ensure the idempotence of the request.

You can use the client to generate the token, but you must make sure that the token is unique among different requests. The token can contain only ASCII characters.

Note If you do not specify this parameter, the system automatically uses the request ID as the client token. The request ID may be different for each request.

Specifies whether to perform only a dry run, without performing the actual request. Valid values:

  • true: checks the request without performing the operation. The system checks the request for potential issues, including missing parameter values, incorrect request syntax, and service limits. If the request fails the dry run, an error code is returned. If the request passes the dry run, the DryRunOperation error code is returned.
  • false (default): performs a dry run and performs the actual request. If the request passes the dry run, a 2xx HTTP status code is returned and the operation is performed.

The ID of the forwarding rule. Valid values of N: 1 to 5.


The ID of the forwarding rule. Valid values of N: 1 to 5.


Response parameters


Deletes one or more forwarding rules at a time.


The asynchronous task ID.


The request ID.



Sample success responses


  "JobId": "72dcd26b-f12d-4c27-b3af-18f6aed5****",
  "RequestId": "7BED4F62-3E6E-5E4F-8C53-2D8CCE77F2ED"

Error codes

HTTP status codeError codeError messageDescription
400IncorrectStatus.RuleThe status of %s [%s] is incorrect.The status of %s [%s] is incorrect.
400OperationDenied.CrossLoadBalancerRulesThe operation is not allowed because of %s.The operation is not allowed because of %s.
404ResourceNotFound.RuleThe specified resource %s is not found.The specified resource %s is not found.

For a list of error codes, visit the Service error codes.

Change history

Change timeSummary of changesOperation
2024-01-29The Error code has changedsee changesets
Change itemChange content
Error CodesThe Error code has changed.
    delete Error Codes: 400
    delete Error Codes: 404
    Added Error Codes: 403