Skip to main content
Create, list, and retrieve datasets and their sequences.

Create Dataset

Creates a new dataset for annotation. You can optionally attach a cloud storage provider configuration to back the dataset with S3 or GCS data.

Request Body

Provider Config (S3)

Request

Response


List Datasets

Returns all user-owned datasets belonging to a specific owner that are visible to the authenticated user.
This endpoint returns datasets owned directly by the user. Organization-owned datasets are not included — use List Organization Datasets instead.

Parameters

Request

Response

Fields


List Organization Datasets

Returns datasets owned by an organization. Only available to organization members and staff.
If your datasets belong to an organization, use this endpoint instead of the user-scoped List Datasets endpoint.

Parameters

Request

Response

Same format as List Datasets.

List Sequences (Single Dataset)

Returns sequences within a single dataset. Used for video and LiDAR datasets that contain frame sequences.

Parameters

Request

Response

Fields


List Sequences (Cross-Dataset)

Returns sequences across all datasets belonging to an owner. Supports filtering by dataset slug(s) and status, making it ideal for bulk QC status checks without per-dataset API calls.

Parameters

Request

Use this endpoint instead of making separate calls to /datasets/{owner}/{slug}/sequences/ for each dataset. This avoids rate limiting when checking QC status across many batches.

Dataset Health

GET /api/v1/datasets/{owner_name}/{dataset_slug}/health/ Read-only ingest and indexing snapshot for a dataset. Designed for programmatic validation after upload: confirm frame totals, sequence counts, and calibration presence without opening Mission Control.

Request

Response

Fields

Typical issues surfaced: dataset not in created status, empty dataset, sequences with zero frames.

Data Types


Dataset Status


Sequence Status Values

Sequences progress through various workflow statuses during the annotation lifecycle.

Error Responses

Not Found (404)

Returned when the specified owner or dataset does not exist.

Permission Denied (403)

Returned when the authenticated user does not have access to the requested dataset.

Unauthorized (401)

Returned when the X-Avala-Api-Key header is missing or contains an invalid key.