> ## Documentation Index
> Fetch the complete documentation index at: https://arize-ax.mintlify.site/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Create a dataset

> Create a new dataset with JSON examples. Empty datasets are not allowed.

**Payload Requirements**
- The dataset name must be unique within the given space.
- Each item in `examples[]` may contain **any user-defined fields**.
- Do not include system-managed fields on input: `id`, `created_at`, `updated_at`.
Requests that contain these fields in any example **will be rejected**.
- Each example **must contain at least one property** (i.e., `{}` is invalid).

**Valid example** (create)
```json
{
  "name": "my-dataset",
  "space_id": "spc_123",
  "examples": [
    {
      "question": "What is 2+2?",
      "answer": "4",
      "topic": "math"
    },
    {
      "question": "What is the capital of Spain?",
      "answer": "Madrid",
      "topic": "geography"
    },
  ]
}
```

**Invalid example** ('id' not allowed on create)
```json
{
  "name": "my-dataset",
  "space_id": "spc_123",
  "examples": [
    {
      "id": "ex_1",
      "input": "Hello"
    }
  ]
}
```

<Note>This endpoint is in beta, read more [here](https://arize.com/docs/ax/rest-reference#api-version-stages).</Note>




## OpenAPI

````yaml https://api.arize.com/v2/spec.yaml post /v2/datasets
openapi: 3.0.3
info:
  title: Arize REST API
  version: 2.0.0
  description: |
    API specification for the backend data server. The API is hosted globally
    at https://api.arize.com/v2 or in your own environment.
  license:
    name: Apache-2.0
    url: https://www.apache.org/licenses/LICENSE-2.0
servers:
  - description: Global
    url: https://api.arize.com
  - description: Regional
    url: https://api.{region}.arize.com
    variables:
      region:
        default: eu-west-1a
        enum:
          - eu-west-1a
          - ca-central-1a
  - description: Custom Host
    url: https://{host}
    variables:
      host:
        default: api.arize.com
security:
  - bearerAuth: []
tags:
  - name: AI Integrations
    description: |
      AI integrations configure access to external LLM providers (e.g. OpenAI,
      Azure OpenAI, AWS Bedrock, Vertex AI). Integrations can be scoped to the
      entire account, a specific organization, or a specific space.
  - name: Annotation Configs
    description: >
      Annotation configs allow you to define consistent annotation schemas that

      can be reused across your workspace, ensuring evaluations are structured
      and

      comparable over time.
  - name: Annotation Queues
    description: >
      Annotation queues help you organize and manage human evaluation workflows.

      Use queues to assign spans or examples to annotators for review and
      labeling.
  - name: API Keys
    description: >
      API keys are used to authenticate requests to the Arize API. List your
      keys

      to view metadata; the raw secret is never returned after creation.
  - name: Datasets
    description: |
      Datasets are structured, version-controlled example collections you use to
      run, evaluate, and track LLM experiments.
  - name: Evaluators
    description: >
      Evaluators are reusable evaluation configurations used to assess the
      quality

      of LLM outputs. They can be template-based (using LLM judges) or
      code-based.
  - name: Experiments
    description: >
      Experiments let you systematically test prompt/model changes using
      datasets,

      tasks, and evaluators.
  - name: Integrations
    description: >
      Integrations configure access to external LLM providers (e.g. OpenAI,

      Azure OpenAI, AWS Bedrock, Vertex AI), notifications services (e.g.
      PagerDuty, Slack), and

      your own agents. Integrations can be scoped to the entire account, a
      specific

      organization, or a specific space.
  - name: Organizations
    description: >
      Organizations are top-level containers within an Arize AX account for
      grouping spaces.
  - name: Projects
    description: |
      Projects represent LLM applications being monitored in Arize where you can
      observe traces and spans.
  - name: Prompts
    description: >
      Prompts are reusable, versioned templates for LLM interactions. Use
      prompts

      to standardize and manage how you interact with LLMs across your
      application.
  - name: Resource Restrictions
    description: |
      Endpoints for restricting and unrestricting resources (projects, models).
  - name: Role Bindings
    description: |
      Role bindings assign a role to a user on a resource. REST currently
      supports space- and project-scoped bindings.
  - name: Roles
    description: >
      Roles define sets of permissions that can be assigned to users within an

      account. Create custom roles to tailor access control to your team's
      needs.
  - name: Spaces
    description: >
      Spaces are containers within an organization for grouping related
      projects,

      datasets, and experiments, enabling collaboration or isolated
      experimentation

      with role-based access control.
  - name: Spans
    description: |
      Spans represent individual operations within a trace. A span captures the
      timing, status, and attributes of a single operation in your application.
  - name: Tasks
    description: |
      Tasks are configurable units of work that tie one or more evaluators to a
      data source (project or dataset). Use tasks to automate evaluation of LLM
      outputs, with support for continuous evaluation and backfill runs.
  - name: Users
    description: >
      Users represent members of an account. The Users endpoints allow creating,

      listing, updating (display name), and removing users from the account
      programmatically.
paths:
  /v2/datasets:
    post:
      tags:
        - Datasets
      summary: Create a dataset
      description: >
        Create a new dataset with JSON examples. Empty datasets are not allowed.


        **Payload Requirements**

        - The dataset name must be unique within the given space.

        - Each item in `examples[]` may contain **any user-defined fields**.

        - Do not include system-managed fields on input: `id`, `created_at`,
        `updated_at`.

        Requests that contain these fields in any example **will be rejected**.

        - Each example **must contain at least one property** (i.e., `{}` is
        invalid).


        **Valid example** (create)

        ```json

        {
          "name": "my-dataset",
          "space_id": "spc_123",
          "examples": [
            {
              "question": "What is 2+2?",
              "answer": "4",
              "topic": "math"
            },
            {
              "question": "What is the capital of Spain?",
              "answer": "Madrid",
              "topic": "geography"
            },
          ]
        }

        ```


        **Invalid example** ('id' not allowed on create)

        ```json

        {
          "name": "my-dataset",
          "space_id": "spc_123",
          "examples": [
            {
              "id": "ex_1",
              "input": "Hello"
            }
          ]
        }

        ```


        <Note>This endpoint is in beta, read more
        [here](https://arize.com/docs/ax/rest-reference#api-version-stages).</Note>
      operationId: datasets_create
      requestBody:
        $ref: '#/components/requestBodies/CreateDatasetRequestBody'
      responses:
        '201':
          $ref: '#/components/responses/Dataset'
        '400':
          $ref: '#/components/responses/BadRequest'
        '401':
          $ref: '#/components/responses/Unauthorized'
        '403':
          $ref: '#/components/responses/Forbidden'
        '404':
          $ref: '#/components/responses/NotFound'
        '409':
          $ref: '#/components/responses/Conflict'
        '422':
          $ref: '#/components/responses/UnprocessableEntity'
components:
  requestBodies:
    CreateDatasetRequestBody:
      description: Body containing dataset creation parameters
      required: true
      content:
        application/json:
          schema:
            required:
              - name
              - space_id
              - examples
            type: object
            properties:
              name:
                type: string
                description: Name of the new dataset
              space_id:
                type: string
                description: ID of the space the dataset will belong to
              examples:
                type: array
                minItems: 1
                maxItems: 1000
                description: Array of examples for the new dataset
                items:
                  $ref: '#/components/schemas/DatasetExampleCreate'
          example:
            name: Math Questions Dataset
            space_id: space_12345
            examples:
              - question: What is 2 + 2?
                answer: '4'
                topic: arithmetic
              - question: What is the square root of 16?
                answer: '4'
                topic: geometry
              - question: If 3x = 12, what is x?
                answer: '4'
                topic: algebra
  responses:
    Dataset:
      description: A dataset object
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Dataset'
          example:
            id: RGF0YXNldDoxOmFCY0Q=
            created_at: '2024-01-01T12:00:00Z'
            updated_at: '2024-01-02T12:00:00Z'
            name: Sample Dataset
            space_id: U3BhY2U6MTphQmNE
            versions:
              - id: RGF0YXNldFZlcnNpb246MTphQmNE
                name: v1.0
                dataset_id: RGF0YXNldDoxOmFCY0Q=
                created_at: '2024-01-01T12:00:00Z'
                updated_at: '2024-01-02T12:00:00Z'
              - id: RGF0YXNldFZlcnNpb246MjphQmNE
                name: v1.1
                dataset_id: RGF0YXNldDoxOmFCY0Q=
                created_at: '2024-02-01T12:00:00Z'
                updated_at: '2024-02-02T12:00:00Z'
    BadRequest:
      description: Invalid request
      content:
        application/problem+json:
          schema:
            $ref: '#/components/schemas/Problem'
          example:
            status: 400
            title: Invalid request parameters
            detail: The 'name' field is required and must be a non-empty string.
            instance: /resource
            type: https://arize.com/docs/ax/rest-reference/errors#invalid-request
    Unauthorized:
      description: Authentication is required
      content:
        application/problem+json:
          schema:
            $ref: '#/components/schemas/Problem'
          example:
            status: 401
            title: Authentication required
            detail: You must be authenticated to access this resource.
            instance: /resource
            type: >-
              https://arize.com/docs/ax/rest-reference/errors#authentication-required
    Forbidden:
      description: Insufficient permissions to access this resource
      content:
        application/problem+json:
          schema:
            $ref: '#/components/schemas/Problem'
          example:
            status: 403
            title: Access forbidden
            detail: You do not have permission to access this resource.
            instance: /resource/12345
            type: https://arize.com/docs/ax/rest-reference/errors#access-forbidden
    NotFound:
      description: Not found
      content:
        application/problem+json:
          schema:
            $ref: '#/components/schemas/Problem'
          example:
            status: 404
            title: Resource not found
            detail: The requested resource with ID '12345' was not found.
            instance: /resource/12345
            type: https://arize.com/docs/ax/rest-reference/errors#resource-not-found
    Conflict:
      description: Resource conflict
      content:
        application/problem+json:
          schema:
            $ref: '#/components/schemas/Problem'
          example:
            status: 409
            title: Resource conflict
            detail: A resource with the given identifier already exists.
            instance: /resource
            type: https://arize.com/docs/ax/rest-reference/errors#resource-conflict
    UnprocessableEntity:
      description: Unprocessable entity
      content:
        application/problem+json:
          schema:
            $ref: '#/components/schemas/Problem'
          example:
            status: 422
            title: Unprocessable Entity
            detail: Minimum score must be less than maximum score.
            instance: /annotation-configs
            type: >-
              https://arize.com/docs/ax/rest-reference/errors#unprocessable-entity
  schemas:
    DatasetExampleCreate:
      type: object
      description: |
        A dataset example with arbitrary user-defined fields. System-managed
        fields are excluded for creation requests.
      additionalProperties: true
    Dataset:
      required:
        - id
        - name
        - space_id
        - created_at
        - updated_at
      type: object
      properties:
        id:
          type: string
          description: Unique identifier for the dataset
        name:
          type: string
          description: Name of the dataset
        space_id:
          type: string
          description: Unique identifier for the space this dataset belongs to
        created_at:
          type: string
          description: Timestamp for when the dataset was created
          format: date-time
        updated_at:
          type: string
          description: Timestamp for the last update of the dataset
          format: date-time
        versions:
          type: array
          items:
            $ref: '#/components/schemas/DatasetVersion'
          description: List of versions associated with this dataset
      description: >
        A dataset is a structured collection of examples used to test and
        evaluate

        LLM applications. Datasets allow you to test models consistently across

        any real-world scenarios and edge cases, quickly identify regressions,

        and track measurable improvements.
      additionalProperties: false
    Problem:
      type: object
      description: RFC 9457 Problem Details
      properties:
        title:
          type: string
          description: A short, human-readable summary of the problem type
        status:
          type: integer
          description: >-
            The HTTP status code generated by the origin server for this
            occurrence of the problem
        type:
          type: string
          format: uri-reference
          description: A URI reference that identifies the problem type
        detail:
          type: string
          description: >-
            A human-readable explanation specific to this occurrence of the
            problem
        instance:
          type: string
          format: uri-reference
          description: >-
            A URI reference that identifies the specific occurrence of the
            problem
      required:
        - title
        - status
      additionalProperties: false
    DatasetVersion:
      required:
        - id
        - name
        - dataset_id
        - created_at
        - updated_at
      type: object
      properties:
        id:
          type: string
          description: Unique identifier for the dataset version
        name:
          type: string
          description: Name of the dataset version
        dataset_id:
          type: string
          description: Unique identifier for the dataset this version belongs to
        created_at:
          type: string
          description: Timestamp for when the dataset version was created
          format: date-time
        updated_at:
          type: string
          description: Timestamp for the last update of the dataset version
          format: date-time
      description: >
        A dataset version is a saved snapshot of a dataset. Arize stores
        datasets

        as version-controlled collections of examples for experiments.

        When you update a dataset, you can do so inplace  or create a new
        version

        while preserving access to previous versions.
      additionalProperties: false
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: <api-key>
      description: >
        Most Arize AI endpoints require authentication. For those endpoints that
        require authentication, include your API key in the request header using
        the format

        ``` Authorization: Bearer <api-key>

        ```

````