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

# Resolve a dataset by name

> Resolve a dataset id from its name within the authenticated project. This is the SDK's entry point, since customer code refers to datasets by name.




## OpenAPI

````yaml /api-reference/openapi.yaml get /v1/datasets/by-name/{name}
openapi: 3.1.0
info:
  title: Zespan Public API
  version: 1.0.0
  description: >
    The Zespan Public API covers the endpoints that customers call directly or
    through the Zespan SDKs: trace ingestion (native and OpenTelemetry), prompt
    management, datasets and dataset runs, and the runtime guardrails check.

    All endpoints authenticate with a project API key sent in the `x-api-key`
    header. Create and manage API keys from the project settings in the Zespan
    dashboard.
servers:
  - url: https://api.zespan.com
    description: Zespan production API
security:
  - ApiKeyAuth: []
tags:
  - name: Ingestion
    description: Send traces and events to Zespan.
  - name: OpenTelemetry
    description: OTLP-compatible ingestion endpoints.
  - name: Prompts
    description: Manage versioned prompts and their labels, tags, and folders.
  - name: Datasets
    description: Read datasets and manage dataset runs used for experiments and scoring.
  - name: Guardrails
    description: Runtime guardrail evaluation.
paths:
  /v1/datasets/by-name/{name}:
    get:
      tags:
        - Datasets
      summary: Resolve a dataset by name
      description: >
        Resolve a dataset id from its name within the authenticated project.
        This is the SDK's entry point, since customer code refers to datasets by
        name.
      operationId: getDatasetByName
      parameters:
        - name: name
          in: path
          required: true
          schema:
            type: string
            minLength: 1
          description: Dataset name.
        - $ref: '#/components/parameters/ProjectIdQuery'
      responses:
        '200':
          description: The resolved dataset.
          content:
            application/json:
              schema:
                type: object
                properties:
                  dataset:
                    type: object
                    properties:
                      id:
                        type: string
                        format: uuid
                      name:
                        type: string
        '401':
          $ref: '#/components/responses/Unauthorized'
        '404':
          $ref: '#/components/responses/NotFound'
components:
  parameters:
    ProjectIdQuery:
      name: projectId
      in: query
      required: false
      schema:
        type: string
        format: uuid
      description: >
        Project id. Optional and ignored when authenticating with an API key,
        since the key already scopes the request to one project.
  responses:
    Unauthorized:
      description: Missing or invalid API key.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
    NotFound:
      description: Resource not found.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
  schemas:
    Error:
      type: object
      properties:
        error:
          type: string
          description: Human-readable error message.
          example: Unauthorized
        code:
          type: string
          description: Machine-readable error code, when present.
          example: rate_limit_exceeded
      required:
        - error
  securitySchemes:
    ApiKeyAuth:
      type: apiKey
      in: header
      name: x-api-key
      description: >-
        Project API key. Manage keys in the Zespan dashboard under project
        settings.

````