JavaScript
Corpus Management
Retrieve Corpus
Fetch the latest metadata for a single corpus by ID.
GET
JavaScript
Overview
Fetch detailed metadata for a single corpus by its unique identifier. This endpoint returns the same comprehensive information as the list endpoint but scoped to one record. Only the corpus owner can retrieve this data.Use this for: Checking indexing status after creation, refreshing UI state after updates, validating corpus existence before operations.
Authentication
Requires valid JWT token or session authentication. You must own the target corpus.Path Parameters
The corpus identifier returned during creation or from the list endpoint.Example:
8d0f0a5d-4b5e-4c09-9db6-0e9d2aa8a9fdExample request
Example response
Response Structure
Unique corpus identifier.
ISO 8601 timestamp when the corpus was created.
Last modification timestamp. Updates when metadata changes or resources are added.
Normalized corpus name (lowercase with underscores).
User-provided description of the corpus purpose.
Storage size in bytes consumed by this corpus and its resources.
Vector database collection identifier where embeddings are stored.
Public visibility flag.
true makes the corpus discoverable by other users.Indexing strategy:
VSI (Vector Store Index), SMI (Summary Index), or DSI (Document Summary Index).Current processing state:
PND- Pending (waiting for resources)PRS- Processing (indexing in progress)IND- Indexed (ready for queries)ERR- Error (indexing failed)
User ID of the corpus owner.
Common Use Cases
Poll for Indexing Completion
Poll for Indexing Completion
After creating a corpus and uploading resources, poll this endpoint to check when indexing completes:
Verify Update Success
Verify Update Success
After modifying corpus settings, fetch the latest state to confirm changes:
Check Storage Usage
Check Storage Usage
Monitor storage consumption before adding more resources:
Validate Before Operations
Validate Before Operations
Ensure corpus exists and is ready before performing operations:
Security Note: Requests return
404 Not Found if the corpus belongs to another user. This prevents leaking corpus existence to unauthorized users.Client examples
- Python
- TypeScript / JavaScript
- Java
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
A UUID string identifying this Corpora.
Response
200 - application/json
The date and time the organization was created
Last updated time
Name of the corpora
Maximum string length:
100Size of the corpora on disk (in bytes)
Location of the index on Remote Storage
Description of the corpora
Is the corpora Visible to all users?
Type of index to be used for the corpora
VSI- VectorStoreIndexSMI- SummaryIndexDSI- DocumentSummaryIndex
Available options:
VSI, SMI, DSI Status of the corpora processing
PND- PendingIQE- In QueuePRS- ProcessingDEX- Data Extracted SuccessfullyDER- Data Extraction ErrorIND- IndexedCMP- CompletedERR- Error
Available options:
PND, IQE, PRS, DEX, DER, IND, CMP, ERR 
