Update Dataset by ID or Tracking ID
One of id or tracking_id must be provided. The auth’ed user must be an owner of the organization to update a dataset.
Authorizations
Headers
The organization id to use for the request
Body
Options for setting up the crawl which will populate the dataset.
The id of the dataset you want to update.
The new name of the dataset. Must be unique within the organization. If not provided, the name will not be updated.
Optional new tracking ID for the dataset. Can be used to track the dataset in external systems. Must be unique within the organization. If not provided, the tracking ID will not be updated. Strongly recommended to not use a valid uuid value as that will not work with the TR-Dataset header.
Lets you specify the configuration for a dataset
The tracking ID of the dataset you want to update.
Response
Timestamp of the creation of the dataset
Flag to indicate if the dataset has been deleted. Deletes are handled async after the flag is set so as to avoid expensive search index compaction.
Unique identifier of the dataset, auto-generated uuid created by Trieve
Name of the dataset
Unique identifier of the organization that owns the dataset
Configuration of the dataset for RAG, embeddings, BM25, etc.
Tracking ID of the dataset, can be any string, determined by the user. Tracking ID's are unique identifiers for datasets within an organization. They are designed to match the unique identifier of the dataset in the user's system.
Timestamp of the last update of the dataset