---
title: "Upsert Ontology Concept"
method: PUT
path: "/knowledge-ontology/{concept_id}"
tags: ["Knowledge"]
---

# Upsert Ontology Concept

`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

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.

## Path parameters

- `concept_id` string, required

## Headers

- `Authorization` string, nullable
- `X-Target-Org-Id` string, nullable

## Request body

- OntologyConceptRequest: Define or redefine one concept in the org's ontology.
  - `concept_type` string, required
  - `concept_id` string, required
  - `title` string, required
  - `body` string, required
  - `ontology` object
  - `trust_tier` string: 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_owner` string, nullable
  - `review_at` string, date-time, nullable
  - `stale_after` string, date-time, nullable: After this, the concept is treated as stale.
  - `sources` OntologySource[]
  - `relationships` OntologyRelationship[]
  - `standard_component_id` string, nullable: The standard-ontology component this maps to, if any.
  - `definition_override` string, nullable
  - `extensions` object

## Response `200`

Successful Response

- ApiResponseSettingsPayload
  - `data` SettingsPayload, 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".
  - `pagination` PaginationMeta
    - `page` integer, required: Current page number (1-indexed)
    - `limit` integer, required: Items per page
    - `total` integer, required: Total number of items
    - `has_next` boolean, required: Whether there are more pages
    - `next_cursor` string, nullable: Opaque cursor for the next page; null when there are no more items. Pass it back as the `cursor` query param to fetch the following page without computing page numbers.
    - `total_available` integer, nullable: Search endpoints only: how many records really match, when known. Can be larger than `total`, which is capped at the 10,000 results that can be paged. For company search this is a distinct-company estimate. Null when unknown; absent outside search.
    - `total_is_lower_bound` boolean, nullable: Search endpoints only: true when more records match than `total` shows (the result set is larger than the 10,000 results that can be paged). Absent outside search.
    - `notes` string[], nullable: Search endpoints only: plain-language notes about the result, e.g. that more records match than can be paged, or that a reversed `between` range was put in order.

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/graph8/apis/graph8-developer-api.md) · [All operations](https://skmtc.dev/graph8/apis/graph8-developer-api/llms.txt) · [OpenAPI document](https://skmtc.dev/graph8/apis/graph8-developer-api/revisions/2e7cfa0ca921?raw)