---
title: "Delete table version records"
method: POST
path: "/v1/table/{id}/version/delete"
tags: ["Table", "Metadata"]
---

# Delete table version records

`POST /v1/table/{id}/version/delete`

Delete version metadata records for table `id`.

This operation deletes version tracking records, NOT the actual table data.
It supports deleting ranges of versions for efficient bulk cleanup.

Special range values:
- `start_version: 0` with `end_version: -1` means delete ALL version records

## Path parameters

- `id` string, required

## Query parameters

- `delimiter` string

## Request body

- BatchDeleteTableVersionsRequest — Request to delete table version records. Supports deleting ranges of versions for efficient bulk cleanup.
  - `identity` Identity — Identity information of a request.
    - `api_key` string — API key for authentication. REST NAMESPACE ONLY This is passed via the `x-api-key` header.
    - `auth_token` string — Bearer token for authentication. REST NAMESPACE ONLY This is passed via the `Authorization` header with the Bearer scheme (e.g., `Bearer <token>`).
  - `context` unknown
  - `id` string[] — The table identifier
  - `branch` string — Branch to target. When not specified, the main branch is used.
  - `ranges` VersionRange[], required — List of version ranges to delete. Each range specifies start (inclusive) and end (exclusive) versions.
    - `start_version` integer, required — Start version of the range (inclusive). Use 0 to start from the first version.
    - `end_version` integer, required — End version of the range (exclusive). Use -1 to indicate all versions up to and including the latest.

## Response `200`

Result of deleting table version records

- BatchDeleteTableVersionsResponse — Response for deleting table version records
  - `context` unknown
  - `deleted_count` integer — Number of version records deleted
  - `transaction_id` string — Optional transaction identifier

## Other responses

- `400` — Indicates a bad request error. It could be caused by an unexpected request body format or other forms of request validation failure, such as invalid json. Usually serves application/json content, although in some cases simple text/plain content might be returned by the server's middleware.
- `401` — Unauthorized. The request lacks valid authentication credentials for the operation.
- `403` — Forbidden. Authenticated user does not have the necessary permissions.
- `404` — A server-side problem that means can not find the specified resource.
- `503` — The service is not ready to handle the request. The client should wait and retry. The service may additionally send a Retry-After header to indicate when to retry.
- `5XX` — A server-side problem that might not be addressable from the client side. Used for server 5xx errors without more specific documentation in individual routes.

---

[API](https://skmtc.net/lance-format/apis/lance-namespace-specification.md) · [All operations](https://skmtc.net/lance-format/apis/lance-namespace-specification/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/lance-format/lance-namespace-specification/versions/f09656f7f568/schema)