Skip to main content
POST
Approve Change
You must have OWNERS write authority on every path the change touches. Self-approval is rejected when a folder rule requires distinct approvers. The change merges to the Ontology only once the required approvals are met; until then the response reports merged: false with the running approval_count / required_approvals.
Two behaviors matter when you describe this control to an auditor:Organization admins hold full Library access, so they count as an Owner of every path for approval purposes even when they are not listed in the folder’s OWNERS file. Your approver population for a governed folder is its declared Owners plus every org admin.An approval rule scoped to a set of author roles applies only to authors holding one of those roles. Any other author is outside the rule, and their changes to that folder apply on their own authority. Leave the author roles empty for a rule that must govern every author.

Authorizations

Authorization
string
header
required

API key or JWT token

Path Parameters

id
string
required

Change ID

Body

application/json
expected_git_ref
string
required

The change git_ref the caller reviewed; a stale value returns 409.

Response

Approval recorded (and merged when the rule is satisfied)

merged
boolean
approval_count
integer<int32>
required_approvals
integer<int32>
already_approved
boolean