Check out release 1.6 with Video Object Tracking

Quick Start

Update scripts and API calls in Label Studio Enterprise

With the new version of Label Studio Enterprise, you must update your scripts and API calls to match new API endpoints and formats. Some endpoints are new, some arguments for existing endpoints are deprecated and removed, and some payloads have changed for POST requests.

Throughout the new version, completions have been renamed annotations. In addition, “Teams” are now called “Workspaces”, to better reflect the fact that they are a way to organize projects, rather than people.

If you rely on existing object IDs (like project_id, task_id, annotation_id, etc.), these were likely changed due to database migration.

Import data

One endpoint has been deprecated and the payload and response have small updates.

Update bulk task import calls

The endpoint /api/projects/<int:project_id>/tasks/bulk still works, but is deprecated and will be removed in the future.

Update calls to that endpoint to use the /api/projects/<project_ID>/import endpoint instead. See the import task data API endpoint documentation.

Update task import payload for pre-annotations

When you import pre-annotations into Label Studio, the completions field is now annotations. See the import task data API endpoint documentation.

Changes to the endpoint response

The endpoint response returns an annotation_count field instead of a completion_count field. If your script expects a response with this field, update it to expect a response with the new field.

If migrated tasks don’t display as expected

Label Studio Enterprise version 2 allows you to upload data before or after you set up the labeling configuration. Because of that, when your data is migrated from version 1 to version 2, some tasks might not display properly. This happens because the data fields for some tasks change from having a reference to the data type of the labeling configuration, such as image, to $undefined$.

If this happens to you, update the affected tasks to use $undefined$ as a key in the task instead of image, text, and so on.

For example:

{'id': 1, 
    {'image': "s3://example.png"}, 
  'meta': {}, 
  'created_at': '2021-08-09T16:00:03.123456Z', 
  'updated_at': '2021-08-09T16:00:03.123456Z', 
  'is_labeled': False, 
  'overlap': 1, 
  'project': 2, 
  'file_upload': None, 
  'annotations': [], 
  'predictions': []

Needs to be updated to the following, with the rest of the task data remaining the same:

{'id': 1, 
    {'$undefined$': "s3://example.png"}, 
  'meta': {}, 

Export data

The export endpoint has changed, and so have the available options for that endpoint and the response parameters. Rather than list all completions for a specific project, use the new export endpoint to see all the task and annotation details for a project.

Updated export endpoint

To export annotations from Label Studio Enterprise, you must call a new endpoint.

Requests made to /api/projects/<project_ID>/results/ or /api/projects/<project_id>/completions/ fail. Instead, call /api/projects/<project_ID>/export?exportType=JSON. See the export API endpoint documentation.

With this change, several arguments are no longer supported:

Deprecated argument New behavior
?aggregator_type= Cannot export aggregated annotations.
?finished=0 No longer a default setting. Instead, use download_all_tasks=true.
?return_task=1 Tasks always returned.
?return_predictions=1 Predictions always returned.
?return_ground_truths=1 Ground truth annotations always returned.

Changes to the endpoint response

In the endpoint response when exporting annotations, the "completions": section is renamed to "annotations".

The content of the response also has some changes:

  • aggregated is removed
  • aggregated_completed_by is removed
  • aggregated_ids is removed
  • result is no longer a double list "result": [[... ]] and is now a single list “result”: [...]
  • completed_by IDs now refer to the actual user IDs (not “expert” IDs as before)

Previous version response

"completions": [ 
   "aggregated": true,
   "aggregated_completed_by": [
   "aggregated_ids": [
   "ground_truth": false,
   "result": [
         "id": "7tHQ-n6xfo",
         "type": "choices",
         "value": {
           "choices": [
         "to_name": "text",
         "from_name": "sentiment"

Current version response


Invite people and create accounts

When you invite people to join your organization, workspace (formerly team), and projects, there are many changes.

Update tokens in use

The old tokens are no longer supported. Make a request reset your organization token used to create invitation links.

See the reset organization token API endpoint documentation.

Updated URL to invite people to your organization

The URL that you use to invite people to your Label Studio Enterprise organization has changed from<token> to http://localhost:8000/user/signup/?token=<token>.

You can generate the token for that URL using the organization invite link API endpoint documentation, then using the response to create the invitation URL.

For example, with the example response:

"token": "111a2b3333cd444e",
"invite_url": "/user/signup/?token=111a2b3333cd444e"

Create an invitation URL of http://localhost:8000/user/signup/?token=111a2b3333cd444e.

Updated flow for inviting project members

Links that invite people directly to projects are no longer supported. Instead, perform the following steps in order:

  1. Invite the person to the organization with the link returned by the organization invite API endpoint.
  2. Change the user’s role to annotator with the organization membership role endpoint.
  3. Add the user to the project by making a POST request to the project member endpoint.

Create and update external and cloud storage

Some endpoints have been updated and some payload parameters are different when performing actions with the storage API.

Updates to storage endpoints

When you want to retrieve information about a storage configuration, specify the type of storage in the API endpoint.

Instead of /api/storages/<int:pk>/, call api/storages/s3?project=<project_ID> for Amazon S3 storage connections for the specific project. See the API documentation to get Amazon S3 storage. You can also call api/storages/s3/<storage_ID> to get the details of a specific storage connection. See the API documentation to get a specific Amazon S3 storage connection.

The same change applies when syncing storage.
Instead of /api/storages/<int:pk>/sync/, call /api/storages/s3/<project_ID>/sync to sync Amazon S3 storage.

Updates to creating or listing storage payload parameters

Some parameters have changed as listed in the following table:

Previous parameter New parameter
path bucket
regex regex_filter
data_key None. Instead, BLOBs are attached to the first available object tag

Create projects

With the change from teams to workspaces, the team_id parameter is no longer supported in the POST payload to create a project using the API.

Instead, do the following:

  1. Create a workspace
    • POST a request to <host>/api/workspaces/ with the following request body:
      "title": "string",
      "description": "string",
      "color": "string",
      "is_personal": true
    • Or retrieve the details of an existing workspace by making a GET request to <host>/api/workspaces/.
  2. Create a project and add it to a workspace.
    • POST a request to <host>/api/projects/ with the following request body. All fields are optional:
      "title": "string",
      "description": "string",
      "label_config": "string",
      "expert_instruction": "string",
      "show_instruction": true,
      "show_skip_button": true,
      "enable_empty_annotation": true,
      "show_annotation_history": true,
      "organization": 0,
      "color": "string",
      "maximum_annotations": -2147483648,
      "is_published": true,
      "model_version": "string",
      "is_draft": true,
      "created_by": {
          "id": 1,
          "first_name": "",
          "last_name": "",
          "email": ""
      "min_annotations_to_start_training": -2147483648,
      "show_collab_predictions": true,
      "sampling": "Sequential sampling",
      "show_ground_truth_first": true,
      "show_overlap_first": true,
      "overlap_cohort_percentage": -2147483648,
      "task_data_login": "string",
      "task_data_password": "string",
      "control_weights": {},
      "evaluate_predictions_automatically": true,
      "workspace": 0
  3. Add a user to a workspace.
    • POST a request to <host>/api/workspaces/{id}/memberships/ with the workspace ID in the path, with the following request body:
      "user": 0,
      "workspace": 0
    • To retrieve a list of users in your organization, make a GET request to <host>/api/users/.