Reorder preset severity rule
Move one preset severity rule to another rule’s position in evaluation order.
Restrictions
Usage
- This moves exactly one rule, not a full reordering:
drag_rule_id’spriorityis set totarget_rule_id’s currentpriority, and every rule between the two original positions — the target rule itself included — shifts by one to close the gap. - Lower
prioritynumbers are evaluated first; moving toward a lower-numbered target moves the rule earlier in evaluation order, and toward a higher-numbered target moves it later. - Returns
ResourceNotFoundif eitherdrag_rule_idortarget_rule_iddoes not exist in the application. - Every call is recorded in the account audit log. Don’t put secrets in request fields.
Authorizations
App key issued from the Flashduty console under Account → APP Keys. Required on every public API call. Keep it secret — it grants the same access as the owning account.
Body
Parameters for moving one rule to another rule's evaluation position.
RUM application ID. Get application IDs via POST /rum/application/list.
ID of the rule being moved. Get rule IDs via POST /rum/issue/preset-severity/rules/list.
ID of the rule whose evaluation position drag_rule_id moves to.
Response
Success
Success response envelope. On every 2xx response, request_id identifies the call (also mirrored in the Flashcat-Request-Id header) and data holds the endpoint-specific payload. Failure responses use a different shape — see ErrorResponse.