Skip to main content
PUT
Validate and save a new governance configuration revision

Authorizations

Authorization
string
header
required

OAuth 2.0 access token obtained through RFC 8628 at /api/auth/device/code and /api/auth/oauth2/token. The API enforces governance:read, session:write, and client-status:write as appropriate.

Body

application/json
base_revision
string<uuid>
required
Example:

"251e6087-98cf-4861-9668-f09f537d5e4d"

managed_yaml
string
required

Extension-free organization policy; published extensions are merged by the server

Response

Saved revision

revision
string<uuid>
required
Example:

"251e6087-98cf-4861-9668-f09f537d5e4d"

yaml
string
required

Validated organization policy template

managed_yaml
string
required

Editable policy projection with extension-owned fields omitted

document
object
required
package_audiences
object
required

Revision-scoped deployment audience keyed by package ID; absent historical records are returned as organization-wide.

created_at
string<date-time>
required