Retrieve a task
Efficiently retrieve detailed task information, including the ability to retrieve a specific task using a task ID. This resourceful functionality allows seamless integration and thorough analysis of tasks, enhancing your workflow's data-driven capabilities. Explore task details effortlessly through this essential endpoint.
Path Params
taskIdstringrequired
Request
import requests
url = "https://api.scale.com/v1/task/576ba74eec471ff9b01557cc"
headers = {"accept": "application/json"}
response = requests.get(url, headers=headers)
print(response.text)
Response
{
"task_id": "601ba74eec471ff9b01557cc",
"created_at": "2021-06-23T09:09:34.752Z",
"callback_url": "http://www.example.com/callback",
"type": "imageannotation",
"status": "canceled",
"instruction": "Label every object in this image",
"params": {
"attachment": "https://example.com/image.jpg",
"geometries": {
"box": {
"objects_to_annotate": [
"vehicle",
"pedestrian"
]
}
}
},
"metadata": {
"key": "value",
"key2": "value2"
}
}
Retrieve Multiple Tasks
This is a paginated endpoint that retrieves a list of your tasks.
The tasks will be returned in descending order based on created_at time. All time filters expect an ISO 8601-formatted string, like '2021-04-25' or '2021-04-25T03:14:15-07:00'
The pagination is based on the limit and next_token parameters, which determine the page size and the current page we are on. The value of next_token is a unique pagination token for each page (nerdy details if you were curious). Make the call again using the returned token to retrieve the next page.
Query Params
start_timestring
The minimum value of created_at for tasks to be returned
Request
import requests
url = "https://api.scale.com/v1/tasks
headers = {"accept": "application/json"}
response = requests.get(url, headers=headers)
print(response.text)
Response
{
"docs": [
{
"task_id": "601ba74eec471ff9b01557cc",
"created_at": "2021-06-23T09:09:34.752Z",
"callback_url": "http://www.example.com/callback",
"type": "imageannotation",
"status": "canceled",
"instruction": "Label every object in this image",
"params": {
"attachment": "https://example.com/image.jpg",
"geometries": {
"box": {
"objects_to_annotate": [
"vehicle",
"pedestrian"
]
}
}
},
"metadata": {
"key": "value",
"key2": "value2"
}
}
],
"total": 220,
"limit": 100,
"has_more": true,
"next_token": "eyJ0YXNrX2lkIjoiNjBkYjgwZTFkYmRkNTMwMDExNDZlMzg5IiwiY3JlYXRlZF9hdCI6IjIwMjEtMDYtMjlUMjA6MjE6NTMuMjg5WiJ9"
}
Cancel Task
You may only cancel pending tasks, and the endpoint will return a 400 error code if you attempt to cancel a completed task
If the task to be cancled had a unique id, specifying clear_unique_id=true
will remove the unique id. Canceling tasks is idempotent such that calling this endpoint multiple times will still return a 200 success response.
Path Params
taskIdstringrequired
Query Params
clear_unique_idstring
If true, will clear a task's unique_id, thus allowing the same unique id to be used in future tasks.
Request
import requests
url = "https://api.scale.com/v1/task/576ba74eec471ff9b01557cc/cancel?clear_unique_id=true"
headers = {"accept": "application/json"}
response = requests.post(url, headers=headers)
print(response.text)
Response
{
"task_id": "601ba74eec471ff9b01557cc",
"created_at": "2021-06-23T09:09:34.752Z",
"callback_url": "http://www.example.com/callback",
"type": "imageannotation",
"status": "canceled",
"instruction": "Label every object in this image",
"params": {
"attachment": "https://example.com/image.jpg",
"geometries": {
"box": {
"objects_to_annotate": [
"vehicle",
"pedestrian"
]
}
}
},
"metadata": {
"key": "value",
"key2": "value2"
}
}
Set Task Metadata
This endpoint sets the metadata
field on a task.
You may set the metadata
field on any existing task using valid key-value data.
Updating a task's metadata
field is idempotent such that calling this endpoint multiple times will still return a 200 success response.
Path Params
taskIdstringrequired
Request
import requests
url = "https://api.scale.com/v1/task/576ba74eec471ff9b01557cc/setMetadata"
headers = {
"accept": "application/json",
"content-type": "application/json"
}
response = requests.post(url, headers=headers)
print(response.text)
Response
{
"task_id": "601ba74eec471ff9b01557cc",
"created_at": "2021-06-23T09:09:34.752Z",
"callback_url": "http://www.example.com/callback",
"type": "imageannotation",
"status": "canceled",
"instruction": "Label every object in this image",
"params": {
"attachment": "https://example.com/image.jpg",
"geometries": {
"box": {
"objects_to_annotate": [
"vehicle",
"pedestrian"
]
}
}
},
"metadata": {
"key": "value",
"key2": "value2"
}
}
Update unique_id
Easily enhance task management and data accuracy with the Scale Update Task Unique ID API endpoint. Seamlessly modify and optimize task identifiers, ensuring your task tracking and organization remain precise and efficient. This endpoint empowers you to maintain data integrity and adaptability, offering a streamlined way to manage unique IDs associated with tasks within your workflow. Explore this versatile endpoint to effortlessly tailor task identification according to your evolving needs.
Path Params
task_idstringrequired
ID of the Task to modify
Body Params
Request
import requests
url = "https://api.scale.com/v1/task/task_id/unique_id"
headers = {
"accept": "application/json",
"content-type": "application/json"
}
response = requests.post(url, headers=headers)
print(response.text)
Response
{
"task_id": "601ba74e98762345bcbcaaaa",
"created_at": "2021-06-23T09:09:34.752Z",
"callback_url": "http://www.example.com/callback",
"type": "imageannotation",
"status": "completed",
"instruction": "Label every object in this image",
"params": {
"attachment": "https://example.com/image.jpg",
"geometries": {
"box": {
"objects_to_annotate": [
"vehicle",
"pedestrian"
]
}
}
},
"unique_id": "new_unique_id"
"metadata": {}
}
Delete unique_id
Enables the secure removal of task identifiers, providing you with enhanced control over your data management processes. You can confidently eliminate obsolete or redundant task unique IDs from your system, maintaining data accuracy and improving workflow organization. Seamlessly integrate this functionality into your task management workflow to ensure your records remain up-to-date and clutter-free. Explore the convenience and flexibility of the Scale Delete Task Unique ID endpoint to optimize your data management practices.
Path Params
task_idstringrequired
ID of the Task to modify
Request
import requests
url = "https://api.scale.com/v1/task/task_id/unique_id"
headers = {"accept": "application/json"}
response = requests.delete(url, headers=headers)
print(response.text)
Response
{
"task_id": "601ba74e98762345bcbcaaaa",
"created_at": "2021-06-23T09:09:34.752Z",
"callback_url": "http://www.example.com/callback",
"type": "imageannotation",
"status": "completed",
"instruction": "Label every object in this image",
"params": {
"attachment": "https://example.com/image.jpg",
"geometries": {
"box": {
"objects_to_annotate": [
"vehicle",
"pedestrian"
]
}
}
},
"metadata": {}
}
Add Task Tag
With this endpoint, you can include a list of tags
to be added to a task. If a tag
is already associated with the task, it will be ignored to avoid duplication. Please note that setting an empty or null string as a tag
is not allowed. Ensure to provide valid non-empty strings in the tags
list to update the task's tags successfully.
Path Params
task_idstringrequired
ID of the Task to modify
Body Params
RAW_BODYarray of strings
List of tags to add to the task
Request
import requests
url = "https://api.scale.com/v1/task/task_id/tags"
headers = {
"accept": "application/json",
"content-type": "application/json"
}
response = requests.put(url, headers=headers)
print(response.text)
Avoiding Duplicate Tasks
Creating duplicate tasks is an issue every team should be mindful to avoid.
Scale AI provides two different mechanisms to prevent duplicate tasks from being created in its task creation endpoints. This allows you to resubmit requests that may have failed in transit or otherwise need to be retried without the risk of creating duplicate tasks.
Option 1: The unique_id
field
The unique_id
field is a field available on every task type Scale provides.
Once a unique_id
has been submitted to Scale, any future task creation requests with the same unique_id
will fail with a 409 error that also conveniently points to the conflicting task.
Values passed into the unique_id
field are permanently associated with the task and will always be returned to you when retrieving tasks from our platform.
You are able to query for tasks directly based on the unique_id
field at any point with our Task Retrieval endpoints.
Best Practices:
unique_id
should be thought of as your own customizable id for a task. Ideally, this id can be easy to look up based on the data you have available on your side. A goodunique_id
might be the filename being submitted, or other types of metadata like a scene or run id that you use internally.unique_id
is set globally across all projects and task types. If you'd like to enforce uniqueness only within a project or task type, we recommend simply prepending or appending the project or task type to the unique id itself, problem solved!
Option 2: The Idempotency-Key
header
To use this feature, provide a header Idempotency-Key: <key>
. You, the client, are responsible for ensuring the uniqueness of your chosen keys. We recommend using V4 UUIDs.
The results of requests specifying an idempotency key are saved. If we later receive a matching request with the same idempotency key, the saved response will be returned, and no additional task will be created. Note that this behavior holds even when the response is an error. Keys are removed after 24 hours.
If an incoming request has the same idempotency key as a saved request, but the two requests do not match in parameters or the users associated with the two requests are different, we will return a 409 error.
In rare situations, we may return a 429 error if two matching requests with identical idempotency keys are made simultaneously. In this case, it is safe to retry.
When would I use this instead of the unique_id
field?
Using the header-based approach is useful in retry logic that catches network or other transient failure modes when you would be immediately retrying the exact same request. Specifically, the feature that allows you to seamlessly get the same task response back if the payload didn't change makes for easier code integrations.
You are able to use both options simultaneously as well.
Workflow Support
Because Unique Ids are permanently tied to a task, this means if something unexpected happened, it can be hard to recover on your own. We have added two features to help support more robust workflows.
Canceling Tasks
When canceling tasks, there is a clear_unique_id
query parameter you can specify on the request. See the Cancel Task endpoint for more details.
Errored Tasks
Sometimes after a task is submitted, it can run into an error, especially in regards to processing attachments.
Everywhere you can specify a unique id, you can also specify clear_unique_id_on_error: true
. As the param name suggests, if the task reaches an error status, the unique id will automatically be unset, such that you could submit a new task with the same new unique id.
Adding unique_id to your payload
{
"unique_id": "s3://bucket/file.png",
"instruction": "Do the thing",
"callback_url": "[email protected]",
...
}
Example 409 Error
{
"status_code": 409,
"error": 'The unique_id ("s3://bucket/file.png") is already used for a different task (602c399c6d092c00115aa3c9).'
}
Example Idempotent Key Header
curl "https://api.scale.com/v1/task/comparison" \
-u "{{ApiKey}}:" \
-H "Idempotency-Key: UNIQUE_IDENTIFIER"
-d callback_url="http://www.example.com/callback" \
...