Skip to main content
POST
/
knowledge
/
content
Upload Content
curl --request POST \
  --url https://api.example.com/knowledge/content \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: multipart/form-data' \
  --form 'name=<string>' \
  --form 'description=<string>' \
  --form 'url=<string>' \
  --form 'metadata=<string>' \
  --form 'file=<string>' \
  --form 'text_content=<string>' \
  --form 'reader_id=<string>' \
  --form 'chunker=<string>' \
  --form file.0='@example-file'
{
  "id": "content-123",
  "name": "example-document.pdf",
  "description": "Sample document for processing",
  "metadata": {
    "category": "documentation",
    "priority": "high"
  },
  "status": "processing"
}

Authorizations

​
Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Query Parameters

​
db_id
string | null

Database ID to use for content storage

Body

multipart/form-data
​
name
string | null

Content name (auto-generated from file/URL if not provided)

​
description
string | null

Content description for context

​
url
string | null

URL to fetch content from (JSON array or single URL string)

​
metadata
string | null

JSON metadata object for additional content properties

​
file
file | null

File to upload for processing

​
text_content
string | null

Raw text content to process

​
reader_id
string | null

ID of the reader to use for content processing

​
chunker
string | null

Chunking strategy to apply during processing

Response

Content upload accepted for processing

​
id
string
required
​
name
string | null
​
description
string | null
​
type
string | null
​
size
string | null
​
linked_to
string | null
​
metadata
Metadata · object
​
access_count
integer | null
​
status
enum<string> | null

Enumeration of possible content processing statuses.

Available options:
processing,
completed,
failed
​
status_message
string | null
​
created_at
string<date-time> | null
​
updated_at
string<date-time> | null