Set tenant rotation policy

Creates or updates the rotation policy for a specific tenant.
This operation is idempotent - it will create if not exists, or update if exists.

Policy rules control algorithm transitions:
• requireOpsSubset: New key must support subset of original operations
• requireNoDowngrade: Prevent transitions to weaker algorithms
• allowClassicalToPqc: Allow RSA/EC → ML-KEM/ML-DSA transitions
• allowPqcToClassical: Allow reverse transitions (usually disabled)
• allowDifferentFamily: Allow ML-KEM → ML-DSA (different families)

Use cases:
• Enforce quantum-safe migration path
• Prevent algorithm downgrades
• Maintain compliance during transitions

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
uuid
required
Body Params

Rotation policy configuration

Request to create a rotation policy

uuid

Template ID to base policy on (technical identifier)

string
length between 1 and 100
^[A-Z0-9_-]+$

Template name (human-readable alternative to templateId)

boolean | null
Defaults to false

Whether the tenant admin may modify this policy. Only meaningful when the deployment is unlocked. Set by platform admin at tenant creation or via PATCH /override-flag.

string
Defaults to 1.0

Model version

boolean | null
Defaults to true

Require that new algorithm supports subset of original operations. Default: true if not provided.

boolean | null
Defaults to true

Require no security level downgrade during rotation. Default: true if not provided.

boolean | null
Defaults to true

Allow classical to PQC algorithm transition. Default: true if not provided.

boolean | null
Defaults to false

Allow PQC to classical algorithm transition. Default: false if not provided.

boolean | null
Defaults to true

Allow rotation to different algorithm family. Default: true if not provided.

mandatoryStandards
array of strings
length between 0 and 20

Mandatory compliance standards to maintain during rotation. Each entry MUST name a standard declared by the platform algorithm catalogue; an unknown value is rejected with HTTP 400 (application/problem+json) whose detail enumerates the accepted values.

mandatoryStandards
customRules
object

Custom validation rules

string
length between 0 and 1000

Administrative notes explaining the reason for this policy change (audit trail)

Headers
string
enum
Defaults to application/json

Generated from available response content types

Allowed:
Response

Language
Credentials
Bearer
JWT
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json
application/problem+json