POST
v1/mgmt/tenant/authaccess/rule/reorderAuthorization
Descope Project ID and Management Key AuthorizationBearer <token>
Project ID:Management Key as bearer token.
In: header
Request Body
application/json
tenantId?string
ruleId?string
position?integer
Format
int32Move one tenant auth access policy rule to a 1-based position in the tenant's evaluation order, shifting the rules in between accordingly. Rules are evaluated first-match in this order.
curl -X POST "https://api.descope.com/v1/mgmt/tenant/authaccess/rule/reorder" \ -H "Content-Type: application/json" \ -d '{}'{ "rules": [ { "id": "string", "name": "string", "description": "string", "enabled": true, "effect": "string", "conditions": [ { "key": "string", "operator": "string", "value": null } ], "createdTime": 0, "modifiedTime": 0, "evaluationOrder": 0, "expireTime": 0 } ]}export interface Response {rules?: {id?: stringname?: stringdescription?: stringenabled?: boolean/** * Evaluation is first-match. */effect?: stringconditions?: AuthAccessCondition[]/** * int32 epoch seconds: proto3 emits int64 as JSON string. See .claude/rules/proto-files.md. */createdTime?: numbermodifiedTime?: number/** * Server-assigned evaluation position (1-based), changed only via the reorder endpoints. */evaluationOrder?: number/** * Epoch seconds after which the rule is no longer evaluated. 0 means never. */expireTime?: number}[]}/** * AuthAccessCondition is one AND-combined condition row of an auth access policy * rule. key is one of: request.ip, request.country, user.email, * user.emailDomain, user.loginId, user.phone. value is a scalar (equal/inCidr) * or a list (in/notIn), carried as a JSON value and validated per key at * write time. */export interface AuthAccessCondition {key?: stringoperator?: string/** * Represents a dynamically typed value which can be either null, a number, a string, a boolean, a recursive struct value, or a list of values. */value?: {[k: string]: unknown}} Was this helpful?