Datasets
Make API calls to manage your datasets.
Last updated
Was this helpful?
Make API calls to manage your datasets.
Last updated
Was this helpful?
Copy your Project Key and your API Token from your project settings and replace them on the API calls you want to use.
There is 1 possible field on this request.
name (required): the name of your new dataset.
There is 1 possible field on this request.
manifest_url (required): the URL of a manifest JSON file containing the URLs of the images to upload along with the dataset split in which it should be placed on (train, valid or test). The maximum manifest json file size is 100MB and 100k (100,000) images. If you need to upload more images, please wait for the previous 100k images to finish uploading before sending a new upload task.
The manifest JSON file must have the following structure.
You can optionally add an external_id field on each image so you can use it as a reference for later operations instead of using our internal IDs.
Keep in mind that this is a time-consuming task, as the Theos backend has to download, downscale (for thumbnails) and upload all your images to our infrastructure.
You will get as a response a task_id to follow the progress of your upload task.
If you want to stop the upload task for any reason, you can run the following request.
There are 3 possible fields on this request.
name (required): the name of your new class.
color (required): the hexadecimal color of your new class.
with_text (optional): whether or not this class will be used for OCR labeling. Possible values are true or false, if not specified it will be false by default.
There is 1 possible field on this request.
db_ids (required): a list of dataset classes DB IDs to delete (1 or more). They're called db_id because the id field on classes refer to their order index, and db_id is their real ID in our database.
Keep in mind that this is a time-consuming task, as the Theos backend has to also delete all the labels of each deleted class from all of your dataset images.
You will get as a response a task_id to follow the progress of your deletion task.
There are 2 possible fields on this request.
name (optional): the new name of your class.
color (optional): the new hexadecimal color of your class.
There are 3 possible fields on this request.
db_ids (required): a list of dataset classes DB IDs to merge (2 or more).
color (required): the hexadecimal color of your new merged class.
name (required): the name of your new merged class.
Keep in mind that this is a time-consuming task, as the Theos backend has to replace all the classes you specified with the new merged class in all of the images of your dataset.
You will get as a response a task_id to follow the progress of your edition task.
In Theos, dataset examples are the pair of image + labels. An example must always have an image, but may not have labels yet.
There are 2 possible fields in this request.
split (optional): the split of the dataset to get examples from. Possible values are train, valid and test. If not specified the default value is train.
page (optional): the page number from which to fetch examples (like on the dataset overview of the Theos UI). Each page contains a maximum of 100 images. Possible values range from 1 to N, where N = (number of examples on the split)/100. When you fetch the first page you will get as part of the response the page_count so you can know how many pages you can go though on your chosen split.
There are 2 possible requests. The first one is using our internal example_id.
The second one is using the external_id that you specified when uploading your image.
There is 1 possible field on this request.
labels (required): the labels to set. They must be in Theos JSON format.
Can be called by specifying our internal example_id.
Or by specifying your external_id.
When labeling, some images won't contain any objects to be labeled, but to mark them as "labeled" you must skip them.
Can be called by specifying our internal example_id.
Or by specifying your external_id.
