> ## 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.
# List tags on a dataset
> List the tags attached to a dataset.
Tags are shared within the space, so the same tag may appear on many
resources. A dataset with no tags returns an empty list rather than a
404.
Requires read access to the dataset. A caller who cannot read it receives
`404`, identical to the response for a dataset that does not exist.
This endpoint is in alpha, read more [here](https://arize.com/docs/ax/rest-reference#api-version-stages).
## OpenAPI
````yaml https://api.arize.com/v2/spec.yaml get /v2/datasets/{dataset_id}/tags
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: Audit Logs
description: >
Audit logs record authenticated user actions within an account, providing
a
chronological trail for security and compliance review. Access requires
account admin privileges and audit logging to be enabled.
- 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: Monitors
description: >
Monitors continuously track a metric over your model or LLM application
data
and alert you when it crosses a threshold. Each monitor watches a single
metric - data quality, model performance, drift, a custom metric, or a
tracing metric - and moves between statuses as the metric passes in and
out of its
healthy range.
- 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: Tags
description: |
Tags are reusable labels defined once per space and attached to resources
across the platform, so the same vocabulary can be applied to projects,
datasets, prompts, and more. Tags are shared: renaming or deleting a tag
affects every resource it is attached to.
- 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: Traces
description: |
A trace is the collection of spans sharing a trace ID, representing a
single end-to-end request through an LLM application. Use the Traces
endpoint to retrieve traces with all of their spans in one call.
- 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.
- name: Webhooks
description: >
Webhooks are organization-owned destinations that receive event deliveries
over HTTPS. Deliveries are authenticated with a bearer token or signed
with
an HMAC signing secret — the secret is returned exactly once, when the
webhook is created. Delivery attempts are recorded and can be listed for
debugging. To choose which events a webhook receives, manage its
subscriptions through the prompt and evaluator webhook-subscription
endpoints.
paths:
/v2/datasets/{dataset_id}/tags:
get:
tags:
- Datasets
summary: List tags on a dataset
description: >
List the tags attached to a dataset.
Tags are shared within the space, so the same tag may appear on many
resources. A dataset with no tags returns an empty list rather than a
404.
Requires read access to the dataset. A caller who cannot read it
receives
`404`, identical to the response for a dataset that does not exist.
This endpoint is in alpha, read more
[here](https://arize.com/docs/ax/rest-reference#api-version-stages).
operationId: list_dataset_tags
parameters:
- $ref: '#/components/parameters/DatasetIdPathParam'
responses:
'200':
$ref: '#/components/responses/ListTagsResponse'
'400':
$ref: '#/components/responses/BadRequest'
'401':
$ref: '#/components/responses/Unauthorized'
'404':
$ref: '#/components/responses/NotFound'
'429':
$ref: '#/components/responses/RateLimitExceeded'
components:
parameters:
DatasetIdPathParam:
name: dataset_id
in: path
description: The unique dataset identifier (base64)
required: true
schema:
$ref: '#/components/schemas/Id'
example: RGF0YXNldDoxMjM0NQ==
responses:
ListTagsResponse:
description: Returns the tags attached to the resource
content:
application/json:
schema:
$ref: '#/components/schemas/ListTagsResponse'
examples:
withTags:
summary: Resource with two tags
value:
tags:
- id: VGFnOjEyMzQ1
name: production
description: Resources serving production traffic
color: GREEN
space_id: U3BhY2U6MTIzNDU=
created_at: '2026-01-01T12:00:00Z'
updated_at: '2026-01-03T09:30:00Z'
- id: VGFnOjEyMzQ2
name: needs-review
description: null
color: null
space_id: U3BhY2U6MTIzNDU=
created_at: '2026-01-01T12:00:00Z'
updated_at: '2026-01-01T12:00:00Z'
pagination:
has_more: false
empty:
summary: Resource with no tags
value:
tags: []
pagination:
has_more: false
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
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
RateLimitExceeded:
description: Rate limit exceeded
headers:
Retry-After:
description: |
When throttled (429), how long to wait before retrying. Value is
either a delta-seconds integer.
schema:
type: integer
minimum: 0
example: 42
content:
application/problem+json:
schema:
$ref: '#/components/schemas/Problem'
example:
status: 429
title: Rate limit exceeded
detail: >-
You have exceeded the allowed number of requests. Please try again
later.
instance: /resource
type: >-
https://arize.com/docs/ax/rest-reference/errors#rate-limit-exceeded
schemas:
Id:
type: string
description: A universally unique identifier (base64-encoded opaque string).
example: RW50aXR5OjEyMzQ1
ListTagsResponse:
type: object
required:
- tags
- pagination
properties:
tags:
type: array
items:
$ref: '#/components/schemas/Tag'
description: >
The tags attached to the resource, most recently updated first.
Empty
when the resource has no tags.
pagination:
allOf:
- $ref: '#/components/schemas/PaginationMetadata'
description: >
Pagination metadata. Tag lists are not paginated yet, so `has_more`
is
always `false` and `next_cursor` is always omitted. The field is
present
so that adding pagination later does not change the response shape.
additionalProperties: false
x-forward-compatible: true
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
x-forward-compatible: true
Tag:
type: object
required:
- id
- name
- space_id
- created_at
- updated_at
properties:
id:
allOf:
- $ref: '#/components/schemas/Id'
description: The unique identifier of the tag
name:
type: string
description: The tag name. Unique within the space, compared case-insensitively.
description:
type: string
nullable: true
description: >
Free-form description of what the tag is for. `null` when no
description
has been set.
color:
allOf:
- $ref: '#/components/schemas/TagColor'
nullable: true
description: >
Display color for the tag. `null` when no color has been assigned,
which
clients render with a neutral treatment.
space_id:
allOf:
- $ref: '#/components/schemas/Id'
description: The unique identifier of the space the tag belongs to
created_at:
type: string
format: date-time
description: When the tag was created
updated_at:
type: string
format: date-time
description: >
When the tag was last modified. Equal to `created_at` until the tag
is
updated.
description: |
A tag is a reusable label defined once per space and attached to many
resources across the platform, so the same vocabulary can be applied to
projects, datasets, prompts, and more.
Tags are shared. Renaming a tag changes it everywhere it appears, and
deleting a tag detaches it from every resource it was attached to.
additionalProperties: false
x-forward-compatible: true
PaginationMetadata:
required:
- has_more
type: object
properties:
next_cursor:
type: string
description: >
Opaque cursor for fetching the next page. Treat as an unreadable
token.
Present when `has_more` is true; omitted when `has_more` is false.
has_more:
type: boolean
description: True if another page of results is available.
description: |
Cursor-based pagination metadata. Use `next_cursor` in the subsequent
request's `cursor` query parameter.
additionalProperties: false
x-forward-compatible: true
TagColor:
type: string
enum:
- GRAY
- INDIGO
- BLUE
- CYAN
- TEAL
- PINE
- GREEN
- LIME
- OLIVE
- LEMON
- YELLOW
- ORANGE
- RED
- CORAL
- PINK
- PLUM
- PURPLE
- BROWN
- AUBURN
description: >
Display color applied to the tag wherever it is shown. One of the
platform's
19 display colors.
securitySchemes:
bearerAuth:
type: http
scheme: bearer
bearerFormat:
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
```
````