Hybrid & On-prem
Cloud data overview
Restrict data access by IP range
How to generate signed URLs
How to generate non-expiring signed URLs
Data import overview
Upload data via app
Import URLs via JSON
Asset metadata & image overlay (beta)
Model-assisted labeling (import annotations)
Real-time human-in-the-loop labeling
Custom label interface
Creating your first project
Project setup script
Python SDK FAQ
Intro to the GraphQL API
Data types overview
Bulk import requests
Legacy vs new editor ontology
Legacy vs new editor JSON exports
Legacy vs new editor hotkeys
Model predictions (legacy)
October 9, 2020
September 25, 2020
August 21, 2020
August 6, 2020
July 6, 2020
June 22, 2020
June 2, 2020
May 19, 2020
April 14, 2020
April 1, 2020
March 3, 2020
February 18, 2020
February 5, 2020
January 17, 2020
Updated by Alex Cota
These are the data types that are referenced the most. See the documentation explorer at https://app.labelbox.com/explorer for more.
A customizable, hierarchical set of reusable Label schemas that can be used across one or more Projects.
An individual within an Organization. Organization admins can set Organization-level or Project-level permissions for each Member.
Top-level entity that contains one or more Members. Each customer account gets its own Organization in Labelbox.
Additional information that can be attached to a Data Row.
A single annotation on a given asset. Encompasses both objects and classifications.
Contains all the defining information for rendering the UI to create a feature of its kind.
A collection of features on a single asset. A label represents an assessment on a Data Row.
Indicates the quality of a given Label as indicated by a user.
Represents an Asset or collection of Assets (including all associated metadata) and all associated Label information.
A collection of data rows. Each asset is assigned to a data row. Datasets can span multiple projects.
Contains all labeling and reviewing work on a Dataset.
An entity representing a subscription to a type of event on the Labelbox platform. Whenever an event of the subscribed-to type occurs, the webhook's endpoint will be sent a notification. Webhooks can be organization-wide or project-based.