Approve Diff
Approve a pending schema graph diff to record a human verdict that the ontology change is acceptable. Sets review_status to approved. Requires write scope.
Approve a schema graph diff to record a human verdict that the structural change between two class versions is acceptable. Approval sets the diff's review_status to approved and stamps who reviewed it and when, closing the item out of the pending review queue.
Approval is an audit action: the version the diff describes already exists, so approving does not modify the class structure. What it gives you is a reviewed ontology trail: every moderate or critical change to a document type carries an explicit human sign-off you can query later.
critical diffs carefully before approving: they contain field removals, incompatible type changes, or large structural reorganizations that may affect downstream consumers relying on the removed or changed fields./v1/schema-graph/diffs/{id}/approvecurl
curl -s -X POST https://api.talonic.com/v1/schema-graph/diffs/diff-uuid-1/approve \
-H "Authorization: Bearer tlnc_your_api_key"Response
Response fields
approved on success.Response
{
"id": "diff-uuid-1",
"review_status": "approved"
}Errors
Error responses
A typical review loop: list status=pending diffs, inspect each diff's added_fields, removed_fields, and type_changes, approve the acceptable ones, and reject the ones that flag noisy or incorrect field discoveries so they stay visible in the audit history as disputed.
Frequently asked questions
Does approving a diff change the class version?+
review_status: "approved" plus reviewer and timestamp); it does not create, modify, or promote versions.Which diffs need manual approval?+
moderate or critical are created as pending and wait for review. Diffs classified safe (additions only) are approved automatically at creation time.Is approving a diff idempotent?+
review_status to approved; calling it again on the same diff leaves it approved and returns the same response.