Documentation Index
Fetch the complete documentation index at: https://api-reference.scale.com/llms.txt
Use this file to discover all available pages before exploring further.
Create Semantic Segmentation Annotation Task
This endpoint creates a**segmentannotation** task. In this task, one of our labelers will view the given image and classify pixels in the image according to the labels provided. You will receive a semantic, pixel-wise, dense segmentation of the image. We also support instance-aware semantic segmentations, also called panoptic segmentation, via LabelDescription objects. The required parameters for this task are **attachment** and **labels**. The **attachment** is a URL to an image you’d like to be segmented. **labels** is an array of strings or LabelDescription objects describing the different types of objects you’d like to segment the image with. You can optionally provide additional markdown-enabled or Google Doc-based instructions via the **instruction** parameter. You can also optionally set **allow_unlabeled** to true, which will allow the existence of unlabeled pixels in the task response - otherwise, all pixels in the image will be classified (in which case it’s important that there are labels for everything in the image, to avoid misclassification). The response you will receive will be a series of images where each pixel’s value corresponds to the label, either via a numerical index or a color mapping. You will also get separate masks for each label for convenience.If the request successful, Scale will return the generated task object, at which point you should store the **task_id** to have a permanent reference to the task.A markdown-enabled string or iframe embed google doc explaining how to do the segmentation. You can use markdown to show example images, give structure to your instructions, and more. See our instruction best practices for more details. For Scale Rapid projects, DO NOT set this field unless you specifically want to override the project level instructions.
The full url (including the scheme
**http://** or **https://**) or email address of the callback that will be used when the task is completed.A URL to the image you’d like to be segmented.
Describes what type of file the attachment is. We currently only support image for the segmentannotation.
An array of strings or LabelDescription objects describing the different types of objects you’d like to be used to segment the image. You may include at most 50 labels.
This field is used to add additional attributes that you would like to capture per annotation. This only applies to instance annotations. See Annotation Attributes for more details about annotation attributes.
Whether or not this image can be completed without every pixel being labeled.
Editable annotations that a task should be initialized with. This is useful when you’ve run a model to prelabel the task and want annotators to refine those prelabels. Review the Segmentation Hypothesis Format for more details.
A set of key/value pairs that you can attach to a task object. It can be useful for storing additional information about the task in a structured format. Max 10KB. See the Metadata section for more detail.
An array of objects in the form of {“attachment”: “<link to actual attachment>”} to show to taskers as a reference. Context images themselves can not be labeled. Context images will appear like this in the UI. You cannot use the task’s attachment url as a context attachment’s url.
A arbitrary ID that you can assign to a task and then query for later. This ID must be unique across all projects under your account, otherwise the task submission will be rejected. See Avoiding Duplicate Tasks for more details.
If set to be true, if a task errors out after being submitted, the unique id on the task will be unset. This param allows workflows where you can re-submit the same unique id to recover from errors automatically
Arbitrary labels that you can assign to a task. At most 5 tags are allowed per task. You can query tasks with specific tags through the task retrieval API.
Create General Video Annotation Task
This endpoint creates a**videoannotation** task. Given a series of images sampled from a video (which we will refer to as “frames”), Scale will annotate each frame with the Geometries (box, polygon, line, point, cuboid, and ellipse) you specify.
The required parameter for this task is **geometries**.
You can optionally provide additional markdown-enabled or Google Doc-based instructions via the **instruction** parameter.
You may also optionally specify **events_to_annotate**, a list of strings describing events section to annotate in the video.
If the request is successful, Scale will return the generated task object, at which point you should store the **task_id** to have a permanent reference to the task.
The name of the batch to associate this task with. Note that if a batch is specified, you need not specify the project, as the task will automatically be associated with the batch’s project. For Scale Rapid projects specifying a batch is required. See Batches section for more details.
A markdown-enabled string or iframe embed google doc explaining how to do the task. You can use markdown to show example images, give structure to your instructions, and more. See our instruction best practices for more details. For Scale Rapid projects, DO NOT set this field unless you specifically want to override the project level instructions.
The full url (including the scheme
**http://** or **https://**) or email address of the callback that will be used when the task is completed.An array of URLs for the frames you’d like to be annotated. These image frames are stitched together to create a video. This is required if attachment_type is image and must be omitted if attachment_type is video.
A URL pointing to the video file attachment. Only the mp4, webm, and ogg formats are supported.
Describes what type of file the attachment(s) are. The only options are image and video.
An object mapping
**box**, **polygon**, **line**, **point**, **cuboid**, or **ellipse** to Geometry objectsSee the Annotation Attributes section for more details about annotation attributes.
The list of events to annotate.
Use this field to define links between annotations. See Links for more details about links.
The number of frames per second to annotate.
The amount of padding in pixels added to the top, bottom, left, and right of each video frame. This allows labelers to extend annotations outside of the frames.
The amount of padding in pixels added to the left and right of each video frame. Overrides
**padding** if set.The amount of padding in pixels added to the top and bottom of each video frame. Overrides padding if set.
Editable annotations that a task should be initialized with. This is useful when you’ve run a model to prelabel the task and want annotators to refine those prelabels. Review the Segmentation Hypothesis Format for more details.
Editable annotations, with the option to be “locked”, that a task should be initialized with. This is useful when you’ve run a model to prelabel the task and want annotators to refine those prelabels. Must contain the annotations field, which has the same format as the annotations field in the response.
Whether or not new annotations can be added to the task if base_annotations are used. If set to true, new annotations can be added to the task in addition to base_annotations. If set to false, new annotations will not be able to be added to the task.
Whether or not base_annotations can be edited in the task. If set to true, base_annotations can be edited by the tasker (position of annotation, attributes, etc). If set to false, all aspects of base_annotations will be locked.
Whether or not base_annotations labels can be edited in the task. If set to true, the label of base_annotations can be edited by the tasker. If set to false, the label will be locked.
Whether or not base_annotations can be removed from the task. If set to true, base_annotations can be deleted from the task. If set to false, base_annotations cannot be deleted from the task.
A set of key/value pairs that you can attach to a task object. It can be useful for storing additional information about the task in a structured format. Max 10KB.
A value of 10, 20, or 30 that defines the priority of a task within a project. The higher the number, the higher the priority.
A arbitrary ID that you can assign to a task and then query for later. This ID must be unique across all projects under your account, otherwise the task submission will be rejected. See Avoiding Duplicate Tasks for more details.
If set to be true, if a task errors out after being submitted, the unique id on the task will be unset. This param allows workflows where you can re-submit the same unique id to recover from errors automatically
Arbitrary labels that you can assign to a task. At most 5 tags are allowed per task. You can query tasks with specific tags through the task retrieval API.
Create Video Playback Annotation Task
This endpoint creates a**videoplaybackannotation** task. In this task, we will view the given video file and draw annotations around the specified objects.
You are required to provide a URL to the video file as the **attachment**. It can be in **mp4**, **webm**, or **ogg** format.
You can optionally provide additional markdown-enabled or Google Doc-based instructions via the **instruction** parameter.
You may optionally specify a **frame_rate**, which will determine how many frames per second will be used to annotate the given video. The default value is **1**.
You may also optionally specify **events_to_annotate**, a list of strings describing events section to annotate in the video.
If the request is successful, Scale will return the generated task object, at which point you should store the **task_id** to have a permanent reference to the task.The name of the batch to associate this task with. Note that if a batch is specified, you need not specify the project, as the task will automatically be associated with the batch’s project. For Scale Rapid projects specifying a batch is required. See Batches section for more details.
A markdown-enabled string or iframe embed google doc explaining how to do the task. You can use markdown to show example images, give structure to your instructions, and more. See our instruction best practices for more details. For Scale Rapid projects, DO NOT set this field unless you specifically want to override the project level instructions.
The full url (including the scheme
**http://** or **https://**) or email address of the callback that will be used when the task is completed.An array of URLs for the frames you’d like to be annotated. These image frames are stitched together to create a video. This is required if attachment_type is image and must be omitted if attachment_type is video.
A URL pointing to the video file attachment. Only the mp4, webm, and ogg formats are supported.
Describes what type of file the attachment(s) are. The only options are image and video.
An object mapping box, polygon, line, point, cuboid, or ellipse to Geometry objects
See the Annotation Attributes section for more details about annotation attributes.
The list of events to annotate.
The duration of the video in seconds. This is ignored if attachment_type is image. Default is full video length.
The number of frames to capture in one second. This is ignored if attachment_type is image.
The start time in seconds. This is ignored if attachment_type is image.
The amount of padding in pixels added to the top, bottom, left, and right of each video frame. This allows labelers to extend annotations outside of the frames.
The amount of padding in pixels added to the left and right of each video frame. Overrides padding if set.
The amount of padding in pixels added to the top and bottom of each video frame. Overrides padding if set.
Editable annotations, with the option to be “locked”, that a task should be initialized with. This is useful when you’ve run a model to prelabel the task and want annotators to refine those prelabels. Must contain the annotations field, which has the same format as the annotations field in the response.
Whether or not new annotations can be added to the task if base_annotations are used. If set to true, new annotations can be added to the task in addition to base_annotations. If set to false, new annotations will not be able to be added to the task.
Whether or not base_annotations can be edited in the task. If set to true, base_annotations can be edited by the tasker (position of annotation, attributes, etc). If set to false, all aspects of base_annotations will be locked.
Whether or not base_annotations labels can be edited in the task. If set to true, the label of base_annotations can be edited by the tasker. If set to false, the label will be locked.
Whether or not base_annotations can be removed from the task. If set to true, base_annotations can be deleted from the task. If set to false, base_annotations cannot be deleted from the task.
A set of key/value pairs that you can attach to a task object. It can be useful for storing additional information about the task in a structured format. Max 10KB.
A value of 10, 20, or 30 that defines the priority of a task within a project. The higher the number, the higher the priority.
A arbitrary ID that you can assign to a task and then query for later. This ID must be unique across all projects under your account, otherwise the task submission will be rejected. See Avoiding Duplicate Tasks for more details.
If set to be true, if a task errors out after being submitted, the unique id on the task will be unset. This param allows workflows where you can re-submit the same unique id to recover from errors automatically
Arbitrary labels that you can assign to a task. At most 5 tags are allowed per task. You can query tasks with specific tags through the task retrieval API.