datasets
Get Dataset Progress
Get the processing status of datasets, together with in-flight progress.
Same dataset/pipeline selection as **GET /v1/datasets/status**, but each
status value is always an object {status, progress} instead of a bare
status — a dedicated endpoint rather than a flag on /status, so neither
endpoint's response shape ever depends on how it was called.
## Query Parameters
- **dataset** (List[UUID]): Dataset UUIDs to check (from GET /api/v1/datasets). Omit to get
status for all datasets you can read.
- **pipeline** (List[str]): Pipeline names to check: 'add_pipeline', 'cognify_pipeline', or
'code_graph_pipeline' (code ingestion via remember content_type='code'). Omit to default
to cognify_pipeline.
## Response
- Single pipeline (default): {dataset_id: {status, progress}}
- Multiple pipelines: {dataset_id: {pipeline_name: {status, progress}}}
**progress** is `null` until the first in-flight progress tick, then an
object with `completed_items`, `total_items`, and `current_stage` —
present only while the pipeline is running; terminal runs (completed/
errored) do not carry a progress snapshot.
## Error Codes
- **409 Conflict**: Error retrieving status (e.g. requesting a dataset you don't have
read permission for)
GET
Get Dataset Progress
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Query Parameters
Dataset UUIDs to check (from GET /api/v1/datasets). Omit to get status for all datasets you can read.
Example:
Pipeline names to check: 'add_pipeline', 'cognify_pipeline', or 'code_graph_pipeline' (code ingestion via remember content_type='code'). Omit to default to cognify_pipeline.
Example:
Response
Successful Response
- Response Get Dataset Progress Api V1 Datasets Status Progress Get
- Response Get Dataset Progress Api V1 Datasets Status Progress Get