---
title: "Create a new table version"
method: POST
path: "/v1/table/{id}/version/create"
tags: ["Table", "Metadata"]
---

# Create a new table version

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

Create a new version entry for table `id`.

This operation supports `put_if_not_exists` semantics.
The operation will fail with 409 Conflict if the version already exists.

## Path parameters

- `id` string, required

## Query parameters

- `delimiter` string

## Request body

- CreateTableVersionRequest — Request to create a new table version entry. This supports `put_if_not_exists` semantics, where the operation fails if the version already exists.
  - `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
  - `version` integer, required — Version number to create
  - `branch` string — Branch to target. When not specified, the main branch is used.
  - `manifest_path` string, required — Path to the manifest file for this version
  - `manifest_size` integer — Size of the manifest file in bytes
  - `e_tag` string — Optional ETag for the manifest file
  - `metadata` unknown
  - `naming_scheme` string — The naming scheme used for manifest files in the `_versions/` directory. Known values: - `V1`: `_versions/{version}.manifest` - Simple version-based naming - `V2`: `_versions/{inverted_version}.manifest` - Zero-padded, reversed version number (uses `u64::MAX - version`) for O(1) lookup of latest version on object stores V2 is preferred for new tables as it enables efficient latest-version discovery without needing to list all versions.

## Response `200`

Result of creating a table version

- CreateTableVersionResponse — Response for creating a table version
  - `context` unknown
  - `transaction_id` string — Optional transaction identifier
  - `version` TableVersion
    - `version` integer, required — Version number
    - `manifest_path` string, required — Path to the manifest file for this version.
    - `manifest_size` integer — Size of the manifest file in bytes
    - `e_tag` string — Optional ETag for optimistic concurrency control. Useful for S3 and similar object stores.
    - `timestamp_millis` integer — Timestamp when the version was created, in milliseconds since epoch (Unix time)
    - `metadata` unknown

## 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.
- `409` — The request conflicts with the current state of the target 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)