The ID of the vector store that the file batch belongs to.
Example:vs_abc123
The ID of the file batch being retrieved.
Example:vsfb_abc123
The ID of the vector store that the file batch belongs to.
Example:vs_abc123
The ID of the file batch being retrieved.
Example:vsfb_abc123
OK
A batch of files attached to a vector store.
The identifier, which can be referenced in API endpoints.
The object type, which is always vector_store.file_batch.
Allowed values:vector_store.files_batch
The Unix timestamp (in seconds) for when the vector store files batch was created.
The ID of the vector store that the File is attached to.
The status of the vector store files batch, which can be either in_progress, completed, cancelled or failed.
Allowed values:in_progresscompletedcancelledfailed
The ID of the vector store that the file batch belongs to.
The ID of the file batch to cancel.
OK
A batch of files attached to a vector store.
The identifier, which can be referenced in API endpoints.
The object type, which is always vector_store.file_batch.
Allowed values:vector_store.files_batch
The Unix timestamp (in seconds) for when the vector store files batch was created.
The ID of the vector store that the File is attached to.
The status of the vector store files batch, which can be either in_progress, completed, cancelled or failed.
Allowed values:in_progresscompletedcancelledfailed
A limit on the number of objects to be returned. Limit can range between 1 and 100, and the default is 20.
Default:20
Sort order by the created_at timestamp of the objects. asc for ascending order and desc for descending order.
Allowed values:ascdesc
Default:desc
A cursor for use in pagination. after is an object ID that defines your place in the list. For instance, if you make a list request and receive 100 objects, ending with obj_foo, your subsequent call can include after=obj_foo in order to fetch the next page of the list.
A cursor for use in pagination. before is an object ID that defines your place in the list. For instance, if you make a list request and receive 100 objects, starting with obj_foo, your subsequent call can include before=obj_foo in order to fetch the previous page of the list.
Filter by file status. One of in_progress, completed, failed, cancelled.
Allowed values:in_progresscompletedfailedcancelled
The ID of the vector store that the files belong to.
The ID of the file batch that the files belong to.
OK
Example:list
A list of files attached to a vector store.
Example:file-abc123
Example:file-abc456
Example:false
A limit on the number of objects to be returned. Limit can range between 1 and 100, and the default is 20.
Default:20
Sort order by the created_at timestamp of the objects. asc for ascending order and desc for descending order.
Allowed values:ascdesc
Default:desc
A cursor for use in pagination. after is an object ID that defines your place in the list. For instance, if you make a list request and receive 100 objects, ending with obj_foo, your subsequent call can include after=obj_foo in order to fetch the next page of the list.
A cursor for use in pagination. before is an object ID that defines your place in the list. For instance, if you make a list request and receive 100 objects, starting with obj_foo, your subsequent call can include before=obj_foo in order to fetch the previous page of the list.
Filter by file status. One of in_progress, completed, failed, cancelled.
Allowed values:in_progresscompletedfailedcancelled
The ID of the vector store that the files belong to.
OK
Example:list
A list of files attached to a vector store.
Example:file-abc123
Example:file-abc456
Example:false
The ID of the vector store for which to create a File.
Example:vs_abc123
A File ID that the vector store should use. Useful for tools like file_search that can access files.
One OfThe chunking strategy used to chunk the file(s). If not set, will use the auto strategy.
The default strategy. This strategy currently uses a max_chunk_size_tokens of 800 and chunk_overlap_tokens of 400.
OK
A list of files attached to a vector store.
The identifier, which can be referenced in API endpoints.
The object type, which is always vector_store.file.
Allowed values:vector_store.file
The total vector store usage in bytes. Note that this may be different from the original file size.
The Unix timestamp (in seconds) for when the vector store file was created.
The ID of the vector store that the File is attached to.
The status of the vector store file, which can be either in_progress, completed, cancelled, or failed. The status completed indicates that the vector store file is ready for use.
Allowed values:in_progresscompletedcancelledfailed
The last error associated with this vector store file. Will be null if there are no errors.
One OfThe strategy used to chunk the file.