---
title: "Create a new namespace"
method: POST
path: "/v1/namespace/{id}/create"
tags: ["Namespace"]
---

# Create a new namespace

`POST /v1/namespace/{id}/create`

Create a new namespace.
A namespace can manage either a collection of child namespaces, or a collection of tables.
There are three modes when trying to create a namespace, to differentiate the behavior when a namespace of the same name already exists:
  * CREATE: the operation fails with 400.
  * EXIST_OK: the operation succeeds and the existing namespace is kept.
  * OVERWRITE: the existing namespace is dropped and a new empty namespace with this name is created.

## Path parameters

- `id` string, required

## Query parameters

- `delimiter` string, nullable — An opaque token that allows pagination for list APIs (e.g. ListNamespaces). For an initial client request for a list API, if the server cannot return all items in one response, or if there are more items than the `pageSize` specified in the client request, the server must return a `nextPageToken` in the response indicating there are more results available. After the initial request, the value of `nextPageToken` from each response must be used by the client as the `pageToken` parameter value for the next request. Clients must interpret either `null`, missing value or empty string value of `nextPageToken` from a server response as the end of the listing results.

## Request body

- CreateNamespaceRequest
  - `name` string, required
  - `parent` string[]
  - `mode` 'CREATE' | 'EXIST_OK' | 'OVERWRITE', required
  - `options` unknown

## Response `200`

Result of creating a namespace

- CreateNamespaceResponse
  - `name` string, required
  - `parent` string[]
  - `properties` 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.
- `406` — Not Acceptable / Unsupported Operation. The server does not support this operation.
- `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

- **2025-07-21** `6790486d1fac` — 11 breaking, 22 warning, 32 info
  - added the new required request property `name`
  - request property `mode` was restricted to a list of enum values
  - the request property `mode` became required
  - removed the required property `code` from the response with the `400` status
  - …61 more

[Change history](https://skmtc.dev/lance-format/apis/lance-namespace-specification/changes/v1/namespace/:id/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/6790486d1fac/schema)