Skip to main content
PATCH
JavaScript

Overview

Update specific corpus fields without affecting others. This is the recommended approach for incremental changes like toggling visibility, updating descriptions, or modifying individual settings.
Recommended for most updates: Only send the fields you want to change. All other fields remain unchanged.
Perfect for single-field updates like toggling is_published or updating descriptions without risk of resetting other values.

Authentication

Requires valid JWT token or session authentication. You must own the target corpus.

Path Parameters

UUID
required
Corpus identifier to partially update.Example: 8d0f0a5d-4b5e-4c09-9db6-0e9d2aa8a9fd

Request Body

Send only the fields you want to modify:
string
New corpus name (will be normalized to lowercase with underscores). Must be unique.Validation: Server automatically normalizes the name.
string
Updated description of the corpus purpose.
boolean
Toggle public visibility. true makes the corpus discoverable by other users.Common use case: Publishing/unpublishing corpora for access control.
string
Change indexing strategy: VSI, SMI, or DSI
Changing this triggers background re-indexing of all resources.
string
Manual status override (advanced use only).
Normally managed automatically by the system. Only modify if coordinating with backend operators.

Example request

Example response

Response Structure

Returns the complete corpus object with your changes applied:
UUID
Unchanged corpus identifier.
timestamp
Updated to reflect when the change was made.
string
Corpus name (updated if you changed it, otherwise unchanged).
string
Updated description if modified, otherwise original value.
boolean
Updated visibility flag if modified, otherwise original value.
string
Updated indexing strategy if modified. If changed, indexing_status may switch to PRS.
string
May change to PRS if re-indexing was triggered by index_type modification.
float
Unchanged storage size.
string
Unchanged vector database collection.
timestamp
Unchanged original creation time.
UUID
Unchanged corpus owner (read-only).

Common Use Cases

The most common PATCH operation - make a corpus public or private:
Use case: Temporarily hiding a corpus during updates or making it available to other users.
Modify the description without affecting any other fields:
Safe: No risk of accidentally changing name, visibility, or index type.
Update multiple corpora efficiently:
Change index strategy while preserving all other settings:
Note: All other fields (name, description, visibility) remain unchanged.
Update only if conditions are met:
Validation: Name uniqueness and index_type enum validation still apply. Invalid values return 400 Bad Request.
Best Practice: Always use PATCH for single-field updates rather than PUT to avoid accidentally resetting fields to defaults.

Client examples

Authorizations

Authorization
string
header
required

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

Path Parameters

id
string<uuid>
required

A UUID string identifying this Corpora.

Body

corpora_name
string

Name of the corpora

Maximum string length: 100
description
string | null

Description of the corpora

is_published
boolean

Is the corpora Visible to all users?

index_type
enum<string>

Type of index to be used for the corpora

  • VSI - VectorStoreIndex
  • SMI - SummaryIndex
  • DSI - DocumentSummaryIndex
Available options:
VSI,
SMI,
DSI
indexing_status
enum<string>

Status of the corpora processing

  • PND - Pending
  • IQE - In Queue
  • PRS - Processing
  • DEX - Data Extracted Successfully
  • DER - Data Extraction Error
  • IND - Indexed
  • CMP - Completed
  • ERR - Error
Available options:
PND,
IQE,
PRS,
DEX,
DER,
IND,
CMP,
ERR

Response

200 - application/json
id
string<uuid>
required
read-only
created_at
string<date-time>
required
read-only

The date and time the organization was created

updated_at
string<date-time>
required
read-only

Last updated time

corpora_name
string
required

Name of the corpora

Maximum string length: 100
size_on_disk
number<double>
required
read-only

Size of the corpora on disk (in bytes)

index_location
string | null
required
read-only

Location of the index on Remote Storage

creator
string<uuid>
required
read-only
description
string | null

Description of the corpora

is_published
boolean

Is the corpora Visible to all users?

index_type
enum<string>

Type of index to be used for the corpora

  • VSI - VectorStoreIndex
  • SMI - SummaryIndex
  • DSI - DocumentSummaryIndex
Available options:
VSI,
SMI,
DSI
indexing_status
enum<string>

Status of the corpora processing

  • PND - Pending
  • IQE - In Queue
  • PRS - Processing
  • DEX - Data Extracted Successfully
  • DER - Data Extraction Error
  • IND - Indexed
  • CMP - Completed
  • ERR - Error
Available options:
PND,
IQE,
PRS,
DEX,
DER,
IND,
CMP,
ERR