Skip to main content
GET
cURL
Knowledge Graphs can be deployed org-wide (accessible to every team in the organization) or deployed to specific teams. Both are accessible via the API and SDK.
  • With an org-scoped API key, control team scope from the request body: pass team_ids on create or update, or filter list with the team_ids query parameter. Omit team_ids on list to see only org-wide Knowledge Graphs.
  • With a team-scoped API key, every request is automatically restricted to the key’s team. Create assigns to that team; list and retrieve return only that team’s Knowledge Graphs; body team_ids is not accepted.

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your Writer API key.

Path Parameters

graph_id
string<uuid>
required

The unique identifier of the Knowledge Graph.

Response

200 - application/json
id
string<uuid>
required

The unique identifier of the Knowledge Graph.

created_at
string<date-time>
required

The timestamp when the Knowledge Graph was created.

name
string
required

The name of the Knowledge Graph.

file_status
graph_file_status · object
required

The processing status of files in the Knowledge Graph.

type
enum<string>
required

The type of Knowledge Graph.

  • manual: files are uploaded via UI or API
  • connector: files are uploaded via a data connector such as Google Drive or Confluence
  • web: URLs are connected to the Knowledge Graph
Available options:
manual,
connector,
web
description
string

A description of the Knowledge Graph.

urls
web_connector_url · object[]

An array of web connector URLs associated with this Knowledge Graph.

team_ids
integer<int64>[]

The team IDs the Knowledge Graph is deployed to. An empty array indicates an org-wide Knowledge Graph accessible to every team in the organization.