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.

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