Knowledge

Upsert Ontology Concept

Define or redefine one concept in the ontology.

An upsert: the same concept_id twice edits rather than duplicating, which makes it safe to retry.

put/knowledge-ontology/{concept_id}

Request

  • Base URL: https://be.graph8.com/api/v1
  • URL: https://be.graph8.com/api/v1/knowledge-ontology/{concept_id}
  • Auth: HTTP bearer

Path parameters

concept_idstring required

Headers

Authorizationstring nullable
X-Target-Org-Idstring nullable

Request body

concept_typestring required
concept_idstring required
titlestring required
bodystring required
ontologyobject
trust_tierstring

How much to trust this definition. Defaults to human-reviewed, matching the app — a concept written through the API is treated as authored, not inferred.

source_ownerstring nullable
review_atstring date-time nullable
stale_afterstring date-time nullable

After this, the concept is treated as stale.

sourcesOntologySource[]
relationshipsOntologyRelationship[]
standard_component_idstring nullable

The standard-ontology component this maps to, if any.

definition_overridestring nullable
extensionsobject

Response

Successful Response

dataSettingsPayload required

An open envelope for a settings object.

Open because an ontology concept and an SSO config both grow fields as the product does, and on a settings read a dropped field reads as "not configured" rather than "we did not tell you".

Changes

No recorded changes to this operation across all 2 revisions of this API.