Skip to main content
POST
Enable or disable a trust policy
Enables the newest revision of a trust policy, or disables any revision, and answers 200 with its id. Enabling re-runs the Console’s validation first; enabling an older revision is 409. policies:manage must be held at the platform scope: policies have no org-unit home, so a key or External App whose grant covers only some org units receives 403, and an agent can never hold the key. The audit event names the credential that decided, as the Console’s names the person. With an Idempotency-Key, a same-key retry within 24 hours returns the recorded answer only while you still hold policies:manage at the platform scope (see Idempotency). See Trust policies.

Authorizations

Authorization
string
header
required

An External App: the JWT it obtains from POST /oauth/token with OAuth2 client_credentials. Pass as Authorization: Bearer <jwt>. An app's static companion key also authenticates as the app, but is deprecated and is not protected by Idempotency-Key.

Headers

Idempotency-Key
string

Optional logical intent key. A same-key retry within 24 hours returns the recorded result without writing again.

Required string length: 1 - 255

Path Parameters

trustPolicyId
string
required

The policy's id, as the list routes return it.

Required string length: 1 - 200

Body

application/json
enabled
boolean
required

true enables the newest revision only; false works on any revision.

Response

The policy's id

data
object
required
meta
object
required