---
title: "Get a Dataset"
method: GET
path: "/v1/datasets/{id}"
tags: ["/datasets"]
---

# Get a Dataset

`GET /v1/datasets/{id}`

Retrieve a dataset by ID. See ['Datasets'](https://docs.cohere.com/docs/datasets) for more information.

## Path parameters

- `id` string, required

## Headers

- `X-Client-Name` string

## Response `200`

A successful response.

- object
  - `dataset` Dataset, required
    - `id` string, required — The dataset ID
    - `name` string, required — The name of the dataset
    - `created_at` string, date-time, required — The creation date
    - `updated_at` string, date-time, required — The last update date
    - `dataset_type` 'embed-input' | 'embed-result' | 'cluster-result' | 'cluster-outliers' | 'reranker-finetune-input' | 'single-label-classification-finetune-input' | 'chat-finetune-input' | 'multi-label-classification-finetune-input' | 'batch-chat-input' | 'batch-openai-chat-input' | 'batch-embed-v2-input' | 'batch-chat-v2-input', required — The type of the dataset
    - `validation_status` 'unknown' | 'queued' | 'processing' | 'failed' | 'validated' | 'skipped', required — The validation status of the dataset
    - `validation_error` string — Errors found during validation
    - `schema` string — the avro schema of the dataset
    - `required_fields` string[]
    - `preserve_fields` string[]
    - `dataset_parts` DatasetPart[] — the underlying files that make up the dataset
      - `id` string, required — The dataset part ID
      - `name` string, required — The name of the dataset part
      - `url` string — The download url of the file
      - `index` integer — The index of the file
      - `size_bytes` integer — The size of the file in bytes
      - `num_rows` integer — The number of rows in the file
      - `original_url` string — The download url of the original file
      - `samples` string[] — The first few rows of the parsed file
    - `validation_warnings` string[] — warnings found during validation
    - `parse_info` ParseInfo
      - `separator` string
      - `delimiter` string
    - `metrics` Metrics
      - `finetune_dataset_metrics` FinetuneDatasetMetrics
        - `trainable_token_count` number — The number of tokens of valid examples that can be used for training.
        - `total_examples` number — The overall number of examples.
        - `train_examples` number — The number of training examples.
        - `train_size_bytes` number — The size in bytes of all training examples.
        - `eval_examples` number — Number of evaluation examples.
        - `eval_size_bytes` number — The size in bytes of all eval examples.
        - `reranker_data_metrics` RerankerDataMetrics
          - `num_train_queries` number — The number of training queries.
          - `num_train_relevant_passages` number — The sum of all relevant passages of valid training examples.
          - `num_train_hard_negatives` number — The sum of all hard negatives of valid training examples.
          - `num_eval_queries` number — The number of evaluation queries.
          - `num_eval_relevant_passages` number — The sum of all relevant passages of valid eval examples.
          - `num_eval_hard_negatives` number — The sum of all hard negatives of valid eval examples.
        - `chat_data_metrics` ChatDataMetrics
          - `num_train_turns` number — The sum of all turns of valid train examples.
          - `num_eval_turns` number — The sum of all turns of valid eval examples.
          - `preamble` string — The preamble of this dataset.
        - `classify_data_metrics` ClassifyDataMetrics
          - `label_metrics` LabelMetric[]
            - `total_examples` number — Total number of examples for this label
            - `label` string — value of the label
            - `samples` string[] — samples for this label

## Other responses

- `400` — This error is returned when the request is not well formed. This could be because: - JSON is invalid - The request is missing required fields - The request contains an invalid combination of fields
- `401` — This error indicates that the operation attempted to be performed is not allowed. This could be because: - The api token is invalid - The user does not have the necessary permissions
- `403` — This error indicates that the operation attempted to be performed is not allowed. This could be because: - The api token is invalid - The user does not have the necessary permissions
- `404` — This error is returned when a resource is not found. This could be because: - The endpoint does not exist - The resource does not exist eg model id, dataset id
- `422` — This error is returned when the request is not well formed. This could be because: - JSON is invalid - The request is missing required fields - The request contains an invalid combination of fields
- `429` — Too many requests
- `498` — This error is returned when a request or response contains a deny-listed token.
- `499` — This error is returned when a request is cancelled by the user.
- `500` — This error is returned when an uncategorised internal server error occurs.
- `501` — This error is returned when the requested feature is not implemented.
- `503` — This error is returned when the service is unavailable. This could be due to: - Too many users trying to access the service at the same time
- `504` — This error is returned when a request to the server times out. This could be due to: - An internal services taking too long to respond

---

[API](https://skmtc.net/cohere-ai/apis/api-reference.md) · [All operations](https://skmtc.net/cohere-ai/apis/api-reference/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/cohere-ai/api-reference/versions/dbed69eda210/schema)