Skip to main content
POST
Move a rule
Moves an ACTIVE or SUSPENDED rule within its current set or into another set. Supply the destination rule_set_id, a semantic position, and the current expected_rule_configuration_version. Scrip renumbers the source and destination sequences in one transaction. Archived rules cannot move.

Authorizations

X-API-Key
string
header
required

API key passed in the X-API-Key header.

Path Parameters

id
string<uuid>
required

Rule ID

Body

application/json

Destination rule set and semantic position

expected_rule_configuration_version
integer
required

Current rule_configuration_version from the configuration read endpoint. A stale value rejects the request.

Required range: x >= 1
Example:

3

position
object
required

Semantic destination within the destination rule set.

rule_set_id
string<uuid>
required

Destination rule-set ID. It may be the rule's current set.

Response

OK

destination_rules
object[]

Complete renumbered sequence in the destination set.

rule
object

Moved rule in its final position.

rule_configuration_version
integer

Resulting program rule-configuration version.

Example:

4

source_rule_set_id
string<uuid>

Rule set that contained the rule before the move.

source_rules
object[]

Complete renumbered sequence left in the source set.