Get the banning rule list

Use this endpoint to get the list of all banning rules.

• The request URL and request body is case-sensitive. All requests must use HTTPS.

• Content-Type: application/json

• The request header must contain the Authorization field. For details, see RESTful authentication.

• A 200 status code indicates success. The response body contains the following parameters:

• If the status code is not 200, the request fails. See the message field in the response body for the reason for this failure. Refer to Response status codes for details.

Best practices for rule management

To maximize the success rate of create, update, and delete operations, query requests are assigned a lower priority. Under poor network conditions, the success rate and accuracy of GET requests may degrade and some request records may be missing from the results.

When you call POST to create a rule where time is not set to 0, use the following best practices to update or delete it later:

• Save the rule ID returned in the POST request on your server, and rely on this ID for subsequent update and delete operations.
• To ensure that you can still obtain the rule ID under poor network conditions, set the timeout for the POST request to 20 seconds or higher. Make sure that the timeout is set to no less than 5 seconds.
• In case the POST request times out or returns a 504 error, use the response of the GET method to obtain the rule ID. If the rule exists, it indicates that the POST request was successful, and you can save the rule ID on your server.