Upsert Vectors
Insert new documents or update existing documents in a vector store.
Upsert Behavior: If a document ID already exists, it will be completely replaced with the new content and metadata. The previous document’s text, embedding, and all metadata fields are discarded. If the ID does not exist, a new document is created.
Document Content: Each document supports several modes:
contentonly: text is automatically embedded using the store’s configured model.embeddingonly: pre-computed embedding vector is used directly. Dimension must match the store’s configuration.- Both
contentandembedding: the pre-computed embedding is stored and text is kept for retrieval/search. - Neither (metadata-only): only metadata is updated on an existing document without re-embedding. If the document does not exist, it will appear as a failure in the batch response.
A store created without an embedding model (dimensions-only) only accepts documents with pre-computed embedding.
Batch Operations: This endpoint supports batch operations with partial success handling and mixed document types (some with raw embeddings, some with content) in the same call.
Metadata: Supports nested metadata with string, number, boolean, object, and array types. Null values are not permitted—omit the field or use an empty string instead.
Documentation Index
Fetch the complete documentation index at: https://docs.gp.scale.com/llms.txt
Use this file to discover all available pages before exploring further.
Authorizations
Headers
Path Parameters
The name of the vector store
Body
Request to upsert documents.
Array of documents to upsert
Response
Successful Response
Response for batch insert/upsert operations.

