Skip to main content
POST
Reorder escalation rules

Restrictions

Usage

  • Rules are evaluated in ascending priority: the first enabled rule whose time_filters and filters match a new incident takes it, and later rules are skipped. This endpoint moves drag_rule_id into target_rule_id’s slot and renumbers the channel’s rules from priority 0, changing that evaluation order.
  • Both drag_rule_id and target_rule_id must be rules of channel_id; otherwise InvalidParameter.
  • An unknown channel_id returns InvalidParameter.
  • Concurrent reorders of the same channel are rejected with TooManyRequests.
  • The caller must also be able to edit the channel: the account owner or an admin, the channel creator, or a member of its managing teams (of its owning team when managing_team_ids is empty). Otherwise the call returns AccessDenied.
  • Every call is recorded in the account audit log.

Authorizations

app_key
string
query
required

APP Key created in the Flashduty console under My → APP Key. Send it as the app_key query parameter or in the Fd-App-Key request header. Its effective access is the intersection of the key's permission scope and the creator's current role permissions. Keep it secret.

Body

application/json
channel_id
integer<int64>
required

Owning channel ID; obtain it from POST /channel/list.

drag_rule_id
string
required

ID of the rule being dragged (24-character hex), as returned in rule_id by the create or list endpoint.

Pattern: ^[0-9a-fA-F]{24}$
target_rule_id
string
required

ID of the rule whose slot the dragged rule moves into (24-character hex).

Pattern: ^[0-9a-fA-F]{24}$

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.

request_id
string
required

Unique ID for this request. Mirrored in the Flashcat-Request-Id response header. Include it when reporting issues.

Example:

"01HK8XQE3Z7JM2NTFQ5YJ8P9R4"

data
object

Operation-specific payload, documented in each operation's 200 response. Operations without a payload return {} or omit data entirely.