Update a custom rule set version

This operation modifies your existing custom rule set version. You can edit rule settings, and add or remove rules within a set. You can modify a version until it's activated. Once you activate a version, you need to create a new one to edit its settings. Custom rules offer detailed control and conditional logic to process requests to your application or service, overriding default settings when specified. Use the environment version's ruleSetOrder array to manage how rule sets execute.

Path Params
string
required

Name of the workspace that unifies all resources for your application or service. You can rename the workspace with a separate operation after you initially create the resource.

string
required

Name of the environment, unique within a workspace. You can't modify it after you initially create it with a POST request.

string
required

A unique name for the rule set.

integer
required

A unique system identifier for a version.

Query Params
string

For customers who manage more than one account, this runs the operation from another account. The Identity and Access Management API provides a list of available account switch keys.

Body Params
rules
array of objects
required

This object flexibly expresses the configuration settings for rules. Its specific structure and set of fields depend on the rule type and your application's requirements. It defines conditions, actions, and other relevant options needed to properly configure the rule for your use case.

rules*
Headers
string
^(\\W)?"

This header prevents accidental overwrites and conflicts by making requests conditional. When you pass in a resource's ETag as an If-Match test, the update succeeds only if the resource hasn't changed. If the current ETag doesn't match and the data has changed, the server responds with a 412 error. See the Concurrency control section for more details.

Response

Language
URL
LoadingLoading…
Response
Choose an example:
application/json