Reorder Support Rules
POST/api/support/admin/rules/reorder
Sets the run order of the automation rules. The listed ids are renumbered 1, 2, 3, ... in the order given; any rule not listed keeps its relative order and is placed after the listed ones. Order matters across all triggers (position is global), and within a trigger it decides which matching rule runs first. Returns the full rule list in the new order, like List Support Rules.
support:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
Request body
ids(integer[], required, 1 to 500) — the rule ids in their new top-to-bottom order.ids[](integer, distinct) — each id must be an existing rule.
Authentication: Bearer token with the support:write scope, or an authenticated session, from a caller with an active support role who also holds the support admin role. No tenant context — this endpoint is central.
Request
Responses
- 200
- 401
- 403
- 422
- 429
OK
Response Headers
Unauthenticated — the bearer token is missing, revoked, expired, or malformed. Never retry automatically; fix the credential. See the Errors guide.
Forbidden
Response Headers
Unprocessable Content
Response Headers
Rate limited — platform limit is 1,000 requests/min; individual tokens may carry lower limits. Honor the Retry-After header before retrying. See the Rate Limits guide.