> ## Documentation Index > Fetch the complete documentation index at: https://docs.fiddler.ai/llms.txt > Use this file to discover all available pages before exploring further. # Get the revision history of a dataset item > Every committed revision of one item, paginated — which version changed it, what that save did to it, when, and by whom. Unlike the other item reads, which return only the item's state at one version, this returns every revision. Revisions written under a version that never committed are excluded, exactly as they are from every other read. Deliberately carries **no item content**: use `GET /evals/datasets/{dataset_id}/items?version=` to read the item as it stood at any one of these versions. `ordering` accepts `version` and `-version`; unrecognised tokens are ignored. Each revision of an item has its own version, so paging through every page returns each revision exactly once. The default is oldest revision first. ## OpenAPI ````yaml GET /v3/evals/datasets/{dataset_id}/items/{item_id}/history openapi: 3.0.3 info: title: Fiddler API - 2.0 description: APIs to interact with Fiddler termsOfService: https://fiddler.ai/about/terms contact: email: support@fiddler.ai license: name: Proprietary url: '2.0' version: '2.0' servers: [] security: - BearerAuth: [] tags: - name: access-key description: CRUD operations for API keys - name: agent-v3 description: CRUD for the Agent Registry (Stage 1, manual entries) - name: aggregation-invalidation-request-v3 description: Endpoints related to retrieving aggregation invalidation requests - name: alert-rules-v3 description: CRUD for Alert Rules, Summary, and Stats APIs - name: application-v3 - name: auth description: Authentication strategies and login flows - name: baseline-v3 description: CRUD for baseline - name: catalog-v3 description: >- Entity catalog provides paginated, searchable discovery of entity names (attribute keys, agent names, span types, span names, score names, evaluator config names) and their distinct values. Powered by ClickHouse materialized views — no worker or PostgreSQL dependency. - name: chart-annotation-v3 description: Endpoints related to retrieving chart annotations - name: chart-v3 description: CRUD for chart - name: queries-v3 description: v3 queries API - name: configuration-v3 description: > Read and change runtime configurations (Config Manager) for your organization, its projects, and its models. **Private preview.** These endpoints accept requests on every deployment. Whether a saved value takes effect depends on two deployment settings that are off by default: one makes Fiddler read stored values, and the other runs the configuration worker, which applies retention changes to stored data. Contact your Fiddler Customer Success Manager before using these endpoints. This reference documents the data retention (TTL) settings: `PROD_EVENTS_TTL_DAYS`, `GENAI_TRACES_TTL_DAYS`, and `GENAI_METRICS_TTL_DAYS`. The API accepts other registered settings too; contact your Fiddler Customer Success Manager before changing any of them. **Retention settings permanently delete data** once it is older than the configured period. When existing data is affected depends on the setting; see each setting's description. - name: cost-evaluators-v3 description: > Paginated roll-up of per-evaluator LLM cost and token usage, aggregated hourly. Available only on deployments with evaluator cost reporting enabled. - name: custom-metrics-v3 - name: dimensionality-reduction-v3 - name: environment-v3 description: Endpoints related to environment management - name: evals - name: datasets - name: evaluation-v3 - name: evaluator-v3 - name: rule-evaluators-v3 - name: experiment-v3 - name: explainability-v3 - name: llm_rca-v3 - name: file-upload description: Endpoints related to file uploading. - name: fql-expressions-v3 description: > Endpoints for listing FQL (Fiddler Query Language) functions available for GenAI custom metrics. Used by the frontend for autocomplete and signature hints in the FQL editor. - name: genai-alert-rules-v3 description: CRUD API for GenAI Alert Rules - name: genai-custom-metrics-v3 description: API for GenAI Custom Metrics - name: genai-filters-v3 description: API for GenAI Filters - name: genai-metrics-v3 description: >- Endpoints for pre-aggregated GenAI metrics. All metric data is pre-aggregated hourly by a Celery-based metric collector; no real-time aggregation is performed at request time. - name: guardrails-api description: Endpoints related to retrieving Guardrails specific data - name: ingestion-v3 - name: intercom-api description: Endpoints related to intercom APIs - name: jobs-v3 - name: llm-gateway-v3 - name: auth-login - name: auth-logout - name: mcp-client-setup-v3 description: Endpoints for retrieving MCP client setup instructions. - name: metrics-v3 description: Metrics endpoints - name: model-v3 - name: dashboard-v3 - name: model-deployment-v3 - name: monitoring-summary-v3 - name: histograms-v3 - name: organization-roles-v3 description: Update user org role - name: organization-settings-v3 description: Update organization settings such as timezone, email configuration, etc. - name: pagerduty-api description: CRUD for Pagerduty services. - name: project-v3 - name: project-roles-v3 description: Project role assignment management - name: scores-v3 description: Unified CRUD for scores and annotations - name: searchable-text-key-v3 description: >- Manage the global searchable text keys table that controls which OTel attribute keys are routed to the full-text-searchable `ValueContent` column in the unified attributes table. Changes propagate to the backing ClickHouse dictionary within 1-2 minutes and affect all tenants. - name: segments-v3 - name: semantic-mapping-v3 description: >- Manage the global semantic name mappings table that maps raw OTel attribute keys to canonical semantic concepts. Changes propagate to the backing ClickHouse dictionary within 1-2 minutes and affect all tenants. - name: server-info-v3 description: Endpoints related to retrieving server information - name: service-account description: > Service accounts and their API keys. A human Org Admin manages the service accounts of their own organization: create, read, update, and enable/disable (there is no delete — an account is disabled instead), and issue, rename, enable/disable, and revoke each account's API keys (a key's expiry is fixed at creation and changed only by rotating the key). An API key is an `fks_` secret that inherits the account's grants and cannot manage service accounts; an active, unexpired key must be disabled before it can be revoked, and it authenticates only while both it and its account are active. Scopes here are capability scopes (what the account may do), not OAuth scopes. - name: sessions-v3 description: v3 session APIs - name: span-v3 - name: team-roles-v3 - name: team-v3 - name: traces-v3 description: v3 trace api for monitoring - name: fetch-sessions-v3 description: v3 fetch sessions api for monitoring - name: user-access-key description: > CRUD operations for user API keys. All endpoints are user-scoped — each user can only operate on their own API keys. No one including Org admins have access to other users' API keys. - name: users-v3 - name: version-compatibility-v3 - name: webhooks externalDocs: url: https://docs.fiddler.ai description: Find out more about Fiddler paths: /v3/evals/datasets/{dataset_id}/items/{item_id}/history: parameters: - name: dataset_id in: path description: Dataset UUID required: true schema: type: string format: uuid - name: item_id in: path description: Dataset item UUID required: true schema: type: string format: uuid get: tags: - evals - datasets summary: Get the revision history of a dataset item description: >- Every committed revision of one item, paginated — which version changed it, what that save did to it, when, and by whom. Unlike the other item reads, which return only the item's state at one version, this returns every revision. Revisions written under a version that never committed are excluded, exactly as they are from every other read. Deliberately carries **no item content**: use `GET /evals/datasets/{dataset_id}/items?version=` to read the item as it stood at any one of these versions. `ordering` accepts `version` and `-version`; unrecognised tokens are ignored. Each revision of an item has its own version, so paging through every page returns each revision exactly once. The default is oldest revision first. operationId: getEvalsDatasetItemHistoryV3 parameters: - $ref: '#/components/parameters/ordering' - $ref: '#/components/parameters/limit' - $ref: '#/components/parameters/offset' responses: '200': description: Paginated list of the item's revisions content: application/json: schema: allOf: - $ref: '#/components/schemas/PaginatedApiResponse' - type: object properties: data: type: object properties: items: type: array items: $ref: '#/components/schemas/DatasetItemRevision' '400': $ref: '#/components/responses/400' '401': $ref: '#/components/responses/401' '403': $ref: '#/components/responses/403' '404': description: >- The dataset does not exist, or it has no committed revision of that item — it never existed, or it belongs to a different dataset. A *deleted* item is not this case: its deletion is a revision, so its history is non-empty and answers 200. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '500': $ref: '#/components/responses/500' components: parameters: ordering: name: ordering in: query description: >- Allows you to order results by any field. For desc order prefix field name with `-` and provide comman separated values for multiple fields required: false schema: type: string limit: name: limit in: query description: Limit for the pagination required: false schema: type: integer offset: name: offset in: query description: Offset for the pagination required: false schema: type: integer schemas: PaginatedApiResponse: type: object description: | Response object for paginated API responses. properties: api_version: type: string default: '3.0' enum: - '2.0' - '3.0' description: | API version of the response. kind: type: string default: PAGINATED enum: - PAGINATED description: | Type of response, indicating a paginated response. data: type: object properties: page_size: type: integer default: 10 example: 10 description: | Number of items per page in the response. item_count: type: integer default: 10 example: 10 description: | Number of items in the current page. total: type: integer example: 100 default: 100 description: | Total number of items across all pages. page_count: type: integer default: 10 example: 10 description: | Total number of pages. page_index: type: integer default: 1 example: 1 description: | Current page index. offset: type: integer default: 0 example: 0 description: | Offset of the first item in the current page. DatasetItemRevision: type: object description: >- One committed save that touched one dataset item. Carries no item content — read the item at `dataset_version.version` to see it. required: - dataset_version - operation - timestamp - created_by properties: dataset_version: allOf: - $ref: '#/components/schemas/DatasetVersionCompact' description: >- The version this revision was written under. Its `version` is for display and `?version=` only; never send it as `base_version`. operation: type: string enum: - created - updated - deleted description: >- What this save did to the item. `deleted` marks the item deleted; an id that is created again after a delete begins a new lifetime and reports `created`, not `updated`. timestamp: type: string format: date-time description: When the revision was written. created_by: allOf: - $ref: '#/components/schemas/UserCompact' description: >- Who saved it. Dataset item revisions carry no author of their own, so this is the author of the version the revision was written under. ErrorResponse: type: object description: | Response object for errors returned by the API. properties: api_version: type: string default: '3.0' enum: - '2.0' - '3.0' description: | API version of the response. kind: type: string default: ERROR enum: - ERROR description: | Type of response, usually indicating an error. error: type: object properties: code: type: integer format: int32 description: > Represents the code for this error, typically an HTTP response code. default: 400 enum: - 400 - 401 - 403 - 404 - 409 - 410 - 422 - 429 - 500 - 501 - 503 message: type: string description: > A human-readable message providing more details about the error. If there are multiple errors, it will be the message for the first error. example: Resource Not Found errors: type: array description: > Container for additional information regarding the error, especially for multiple errors. items: type: object properties: reason: type: string description: > Unique identifier for this error, different from the error code. example: ResourceNotFoundException message: type: string description: > A human-readable message providing more details about the error. If there is only one error, this field will match error.message. example: Resource Not Found help: type: string description: > Link to support or documentation providing more information on the error. DatasetVersionCompact: type: object title: DatasetVersionCompact description: > Compact version of an evaluation dataset version which can be included in the response of relevant APIs. required: - id - version - tag properties: id: type: string format: uuid description: | Unique identifier of the dataset version. version: type: integer description: > Per-dataset version number, accepted by the `version` query parameter. tag: type: string nullable: true description: | Reserved for future version tagging; always null today. UserCompact: type: object title: UserCompactV3 description: > Compact version of a user which can be included in the response of relevant APIs. required: - id - email properties: id: type: string format: uuid readOnly: true description: | Unique identifier for the user. full_name: type: string readOnly: true description: | Full name of the user. email: type: string format: email description: | Email address of the user. responses: '400': description: Bad Request content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '401': description: Unauthorized content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '403': description: Forbidden content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '500': description: Internal Server Error content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' securitySchemes: BearerAuth: type: http scheme: bearer ````