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

# Create a new branch

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

Create a new branch for table `id` starting from a source ref (another
branch and/or version), defaulting to the latest version of the main branch.

## Path parameters

- `id` string, required

## Query parameters

- `delimiter` string

## Request body

- CreateTableBranchRequest
  - `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[]
  - `name` string, required — Name of the branch to create
  - `from_branch` string — Source branch to create the new branch from. When omitted, the new branch is created from the main branch.
  - `from_version` integer — Version of the source (branch or main) to create from. When omitted, the latest version of the source is used.

## Response `200`

Create branch response

- CreateTableBranchResponse — Response for create branch operation
  - `context` unknown
  - `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.
- `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.

## Changes

- **2026-07-01** `591cd95574b0` — 8 info
  - added the optional property `context` to the response with the `200` status
  - added the optional property `context` to the response with the `400` status
  - added the optional property `context` to the response with the `401` status
  - added the optional property `context` to the response with the `403` status
  - …4 more
- **2026-06-05** `9932582b6bd7` — 1 info
  - endpoint added
- **2025-07-21** `6790486d1fac` — 1 breaking
  - api path removed without deprecation

[Change history](https://skmtc.dev/lance-format/apis/lance-namespace-specification/changes/v1/table/:id/branches/create/post.md)

---

[API](https://skmtc.dev/lance-format/apis/lance-namespace-specification.md) · [All operations](https://skmtc.dev/lance-format/apis/lance-namespace-specification/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/lance-format/lance-namespace-specification/revisions/6add052ac039/schema)