Create and manage a Knowledge Graph

Knowledge Graph, our graph-based retrieval-augmented generation (RAG), achieves higher accuracy than traditional RAG approaches that use vector retrieval. This guide will help you understand and use the Knowledge Graph API to integrate RAG capabilities into your agents.

You need an API key to access the Writer API. Get an API key by following the steps in the API quickstart.We recommend setting the API key as an environment variable in a .env file with the name WRITER_API_KEY.

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.

Create a Knowledge Graph

A Knowledge Graph is a collection of files that are used to answer questions. To start working with a Knowledge Graph, create an empty Knowledge Graph that you can add files to. Endpoint: POST https://api.writer.com/v1/graphs

curl --location --request POST https://api.writer.com/v1/graphs \
  --header "Authorization: Bearer $WRITER_API_KEY" \
  --header "Content-Type: application/json" \
  --data-raw '{
    "name": "Financial Reports",
    "description": "Knowledge Graph of 2024 financial reports"
    }'

from writerai import Writer

# Initialize the Writer client. If you don't pass the `api_key` parameter,
# the client looks for the `WRITER_API_KEY` environment variable.
client = Writer()

graph_create_response = client.graphs.create(
    name="Financial Reports",
    description="Knowledge Graph of 2024 financial reports"
)

import { Writer } from "writer-sdk";

// Initialize the Writer client. If you don't pass the `api_key` parameter,
// the client looks for the `WRITER_API_KEY` environment variable.
const client = new Writer();

const graphCreateResponse = await client.graphs.create({
  name: "Financial Reports",
  description: "Knowledge Graph of 2024 financial reports"
});

Request body

The request body is a JSON object that contains the following fields:

Parameter	Type	Description
`name`	string	The name of the Knowledge Graph.
`description`	string	The description of the Knowledge Graph. The description should help the model understand the purpose of the Knowledge Graph and when it should be used.
`team_ids`	array[integer]	Optional. Team IDs to deploy the Knowledge Graph to. Omit or pass an empty array to create an org-wide Knowledge Graph (the default). Provide one or more team IDs to deploy it to those teams. Only accepted from org-scoped API keys; requests made with a team-scoped API key ignore this field and always assign the Knowledge Graph to that key’s team.

Response format

The response has the following structure:

Parameter	Type	Description
`id`	string	The ID of the Knowledge Graph.
`created_at`	string	The date and time the Knowledge Graph was created.
`name`	string	The name of the Knowledge Graph.
`description`	string	The description of the Knowledge Graph.
`team_ids`	array[integer]	The team IDs the Knowledge Graph is deployed to. An empty array indicates an org-wide Knowledge Graph.

{
  "id": "6029b226-1ee0-4239-a1b0-cdeebfa3ad5a",
  "created_at": "2024-06-24T12:34:56Z",
  "name": "Financial Reports",
  "description": "Knowledge Graph of 2024 financial reports",
  "team_ids": []
}

Deploy a Knowledge Graph to specific teams

Pass one or more team IDs in the team_ids array to deploy a new Knowledge Graph to those teams instead of the whole organization. Members of any listed team can use the Knowledge Graph; members of other teams cannot.

curl --location --request POST https://api.writer.com/v1/graphs \
  --header "Authorization: Bearer $WRITER_API_KEY" \
  --header "Content-Type: application/json" \
  --data-raw '{
    "name": "Sales enablement",
    "description": "Deal decks and objection handling for the Sales team",
    "team_ids": [42, 43]
    }'

from writerai import Writer

client = Writer()

graph = client.graphs.create(
    name="Sales enablement",
    description="Deal decks and objection handling for the Sales team",
    team_ids=[42, 43],
)

import { Writer } from "writer-sdk";

const client = new Writer();

const graph = await client.graphs.create({
  name: "Sales enablement",
  description: "Deal decks and objection handling for the Sales team",
  team_ids: [42, 43]
});

To find team IDs, open a team in AI Studio and copy the numeric ID from the URL. To later change the team assignment of an existing Knowledge Graph, see Update team assignment.

Find your Knowledge Graph ID using one of these methods:

Call the Knowledge Graph list endpoint to retrieve all Knowledge Graphs with their IDs.
Locate the ID in the URL of the Knowledge Graph page in AI Studio.

Add a file to a Knowledge Graph

Once you’ve created a Knowledge Graph, you can add files to it. The files you add to a Knowledge Graph are used to answer questions and enhance the accuracy of the responses from the LLM You must upload the file to the Writer API before adding it to a Knowledge Graph. See Manage files for more information about how to upload files. Endpoint: POST /v1/graphs/{graph_id}/file

curl --location --request POST https://api.writer.com/v1/graphs/{graph_id}/file \
--header "Authorization: Bearer $WRITER_API_KEY" \
--header "Content-Type: application/json" \
--data-raw '{"file_id":"1862f090-a281-48f3-8838-26c1e78b605e"}'

from writerai import Writer

# Initialize the Writer client. If you don't pass the `api_key` parameter,
# the client looks for the `WRITER_API_KEY` environment variable.
client = Writer()

graph_file = client.graphs.add_file_to_graph(
  graph_id="{graph_id}",
  file_id="1862f090-a281-48f3-8838-26c1e78b605e",
)

import { Writer } from "writer-sdk";

// Initialize the Writer client. If you don't pass the `api_key` parameter,
// the client looks for the `WRITER_API_KEY` environment variable.
const client = new Writer();

const file = await client.graphs.addFileToGraph('{graph_id}', {
  file_id: '1862f090-a281-48f3-8838-26c1e78b605e',
});

The response will have this structure:

{
  "id": "1862f090-a281-48f3-8838-26c1e78b605e",
  "created_at": "2024-07-01T20:41:44.159505Z",
  "name": "test.txt",
  "graph_ids": [
    "6029b226-1ee0-4239-a1b0-cdeebfa3ad5a"
  ]
}

Path parameters

Parameter	Description
`graph_id`	The ID of the Knowledge Graph to update.

Request body

The request body is a JSON object that contains the following fields:

Parameter	Description
`file_id`	The ID of the file to add to the Knowledge Graph.

You must upload the file to the Writer API before adding it to a Knowledge Graph. See Manage files for more information about how to upload files.

Remove a file from a Knowledge Graph

Endpoint: DELETE /v1/graphs/{graph_id}/file/{file_id}

curl --location --request DELETE "https://api.writer.com/v1/graphs/{graph_id}/file/{file_id}" \
--header "Authorization: Bearer $WRITER_API_KEY"

from writerai import Writer

# Initialize the Writer client. If you don't pass the `api_key` parameter,
# the client looks for the `WRITER_API_KEY` environment variable.
client = Writer()

client.graphs.remove_file_from_graph(
    graph_id="{graph_id}",
    file_id="{file_id}"
)

import { Writer } from "writer-sdk";

// Initialize the Writer client. If you don't pass the `api_key` parameter,
// the client looks for the `WRITER_API_KEY` environment variable.
const client = new Writer();

const file = await client.graphs.removeFileFromGraph('{graph_id}', '{file_id}');

Path parameters

Parameter	Description
`graph_id`	The ID of the Knowledge Graph to update.
`file_id`	The ID of the file to remove from the Knowledge Graph.

Response format

The response has this structure:

{
  "id": "1862f090-a281-48f3-8838-26c1e78b605e",
  "deleted": true
}

List Knowledge Graphs by team

Retrieve Knowledge Graphs in an organization with the list endpoint. By default, the response contains only org-wide Knowledge Graphs. To also include Knowledge Graphs deployed to specific teams, pass those team IDs in the team_ids query parameter. Endpoint: GET /v1/graphs

# Org-wide only (default)
curl --location "https://api.writer.com/v1/graphs" \
  --header "Authorization: Bearer $WRITER_API_KEY"

# Also include Knowledge Graphs deployed to team 42 or team 43
curl --location "https://api.writer.com/v1/graphs?team_ids=42&team_ids=43" \
  --header "Authorization: Bearer $WRITER_API_KEY"

from writerai import Writer

client = Writer()

# Org-wide only (default)
org_wide = client.graphs.list()

# Filtered to specific teams
team_scoped = client.graphs.list(team_ids=[42, 43])

import { Writer } from "writer-sdk";

const client = new Writer();

// Org-wide only (default)
for await (const graph of client.graphs.list()) {
  console.log(graph.id);
}

// Filtered to specific teams
for await (const graph of client.graphs.list({ team_ids: [42, 43] })) {
  console.log(graph.id);
}

Omitting team_ids returns only org-wide Knowledge Graphs. Knowledge Graphs deployed to specific teams do not appear in an unfiltered list; the caller must opt in by passing team_ids. Team-scoped API keys are the exception: those requests always return only that key’s team, regardless of team_ids.

Update team assignment

Change the teams a Knowledge Graph is deployed to by including team_ids in a PUT /v1/graphs/{graph_id} request. The array you pass replaces the whole team assignment:

Omit team_ids to leave the current team assignment unchanged.
Pass one or more team IDs to scope the Knowledge Graph to exactly those teams.
Pass an empty array ([]) to remove every team assignment and make the Knowledge Graph org-wide again.

Team-scoped API keys cannot change the team assignment of a Knowledge Graph; the field is only accepted from org-scoped API keys.

# Move a Knowledge Graph from org-wide to Sales and Marketing teams
curl --location --request PUT "https://api.writer.com/v1/graphs/{graph_id}" \
  --header "Authorization: Bearer $WRITER_API_KEY" \
  --header "Content-Type: application/json" \
  --data-raw '{"team_ids": [42, 43]}'

# Move it back to org-wide
curl --location --request PUT "https://api.writer.com/v1/graphs/{graph_id}" \
  --header "Authorization: Bearer $WRITER_API_KEY" \
  --header "Content-Type: application/json" \
  --data-raw '{"team_ids": []}'

from writerai import Writer

client = Writer()

client.graphs.update("{graph_id}", team_ids=[42, 43])
client.graphs.update("{graph_id}", team_ids=[])

import { Writer } from "writer-sdk";

const client = new Writer();

await client.graphs.update("{graph_id}", { team_ids: [42, 43] });
await client.graphs.update("{graph_id}", { team_ids: [] });

Use a team-scoped API key

Team-scoped API keys restrict every Knowledge Graph API request to a single team, without any per-request configuration. They are useful when a team owns its own API integration and should not see other teams’ Knowledge Graphs. When a team-scoped API key is used:

POST /v1/graphs automatically assigns the new Knowledge Graph to the key’s team. Passing team_ids in the request body is rejected.
PUT /v1/graphs/{graph_id} cannot change the team assignment of a Knowledge Graph. Passing team_ids in the request body is rejected.
GET /v1/graphs/{graph_id}, DELETE /v1/graphs/{graph_id}, and the file endpoints return only Knowledge Graphs deployed to the key’s team. Org-wide Knowledge Graphs and Knowledge Graphs deployed to other teams are not visible.
GET /v1/graphs returns only Knowledge Graphs deployed to the key’s team. Passing team_ids in the query string is only accepted when it matches the key’s team.

Create team-scoped API keys the same way you create org-scoped API keys, then select the team the key applies to. Existing org-scoped API keys continue to work exactly as before.

Add URLs to a Knowledge Graph

You can add URLs to a Knowledge Graph to enhance the model’s knowledge with content from websites. The LLM can then query and use this information when responding to questions. This example adds a web connector URL to a Knowledge Graph. It first retrieves the Knowledge Graph to see the current URLs and then adds a new URL to the Knowledge Graph. Note that this operation replaces the entire list of URLs attached to the Knowledge Graph, which is why it is important to retrieve the existing list of URLs first.

# 1. First, retrieve the current Knowledge Graph to see existing URLs
curl --location 'https://api.writer.com/v1/graphs/{graph_id}' \
    --header "Authorization: Bearer $WRITER_API_KEY"

# 2. Then, send a new request with all the URLs you want to add. In this example, there were no existing URLs, so it's adding a single URL.
curl --location --request PUT 'https://api.writer.com/v1/graphs/{graph_id}' \
    --header 'Content-Type: application/json' \
    --header "Authorization: Bearer $WRITER_API_KEY" \
    --data '{
        "urls": [
            {
                "url": "https://example.com/documentation",
                "type": "sub_pages",
                "exclude_urls": [
                    "https://example.com/documentation/admin",
                    "https://example.com/documentation/private"
                ]
            }
        ]
    }'

from writerai import Writer

# Initialize the Writer client. If you don't pass the `api_key` parameter,
# the client looks for the `WRITER_API_KEY` environment variable.
client = Writer()

graph_id = "GRAPH_ID"

graph = client.graphs.retrieve(graph_id)
urls = graph.urls

urls.append({
    "url": "https://example.com/documentation",
    "type": "sub_pages",
    "exclude_urls": ["https://example.com/documentation/admin", "https://example.com/documentation/private"]
})

client.graphs.update(graph_id, urls=urls)

print(client.graphs.retrieve(graph_id).urls)

import { Writer } from "writer-sdk";

// Initialize the Writer client. If you don't pass the `apiKey` parameter,
// the client looks for the `WRITER_API_KEY` environment variable.
const client = new Writer();

const graph_id = "GRAPH_ID";

const graph = await client.graphs.retrieve(graph_id);

const urls = graph.urls;

urls.push({
  url: 'https://example.com/documentation',
  type: 'sub_pages',
  exclude_urls: [
    'https://example.com/documentation/admin',
    'https://example.com/documentation/private'
  ]
});

const response = await client.graphs.update(graph_id, { urls });

const updatedGraph = await client.graphs.retrieve(graph_id);

console.log(updatedGraph.urls);

See more examples in Add URLs to a Knowledge Graph.

Add a Knowledge Graph to a no-code agent

After you’ve created a Knowledge Graph, you can add it to a no-code agent to add RAG capabilities. You can use this endpoint to add or remove Knowledge Graphs from a no-code agent. Endpoint: PUT /v1/applications/{application_id}/graphs

curl --location --request PUT "https://api.writer.com/v1/applications/{application_id}/graphs" \
--header "Authorization: Bearer $WRITER_API_KEY" \
--header "Content-Type: application/json" \
--data-raw '{"graph_id":"6029b226-1ee0-4239-a1b0-cdeebfa3ad5a"}'

from writerai import Writer

# Initialize the Writer client. If you don't pass the `api_key` parameter,
# the client looks for the `WRITER_API_KEY` environment variable.
client = Writer()

client.applications.graphs.update(
    application_id="{application_id}",
    graph_ids=["{graph_id}"]
)

import { Writer } from "writer-sdk";

// Initialize the Writer client. If you don't pass the `api_key` parameter,
// the client looks for the `WRITER_API_KEY` environment variable.
const client = new Writer();

client.applications.graphs.update('{application_id}', ['{graph_id}']);

Path parameters

Parameter	Description
`application_id`	The ID of the no-code agent to update.

Request body

The request body is a JSON object that contains the following fields:

Parameter	Type	Description
`graph_ids`	array[string]	The IDs of the Knowledge Graphs to associate with the no-code agent.

This method updates the associated Knowledge Graphs to the exact list of IDs provided in the request. To remove a single Knowledge Graph from the no-code agent, set the graph_ids parameter to an array containing the IDs of all the other Knowledge Graphs associated with the no-code agent, excluding the ID of the Knowledge Graph to remove. To remove all Knowledge Graphs from the no-code agent, set this parameter to an empty array.

Response format

The response contains the new list of IDs of the Knowledge Graphs associated with the no-code agent.

{
  "graph_ids": [
    "6029b226-1ee0-4239-a1b0-cdeebfa3ad5a"
  ]
}

Next steps

Learn how to ask your Knowledge Graph questions in a chat completion via tool calling
Query your Knowledge Graph directly using the question endpoint
Fine-tune how your Knowledge Graph searches and retrieves content using the query_config parameter in the Knowledge Graph query configuration guide

Getting started

Monitor and manage

Core concepts

Models and pricing

Connect to your data

Chat completions

No-code agents

Knowledge Graphs

Tool calling

Additional capabilities

Integrations

Security and compliance

Resources

Create and manage a Knowledge Graph

Create a Knowledge Graph

Request body

Response format

Deploy a Knowledge Graph to specific teams

Add a file to a Knowledge Graph

Path parameters

Request body

Remove a file from a Knowledge Graph

Path parameters

Response format

List Knowledge Graphs by team

Update team assignment

Use a team-scoped API key

Add URLs to a Knowledge Graph

Add a Knowledge Graph to a no-code agent

Path parameters

Request body

Response format

Next steps

​Create a Knowledge Graph

​Request body

​Response format

​Deploy a Knowledge Graph to specific teams

​Add a file to a Knowledge Graph

​Path parameters

​Request body

​Remove a file from a Knowledge Graph

​Path parameters

​Response format

​List Knowledge Graphs by team

​Update team assignment

​Use a team-scoped API key

​Add URLs to a Knowledge Graph

​Add a Knowledge Graph to a no-code agent

​Path parameters

​Request body

​Response format

​Next steps

Create a Knowledge Graph

Request body

Response format

Deploy a Knowledge Graph to specific teams

Add a file to a Knowledge Graph

Path parameters

Request body

Remove a file from a Knowledge Graph

Path parameters

Response format

List Knowledge Graphs by team

Update team assignment

Use a team-scoped API key

Add URLs to a Knowledge Graph

Add a Knowledge Graph to a no-code agent

Path parameters

Request body

Response format

Next steps