---
title: "Register a table to a namespace"
method: POST
path: "/v1/table/{id}/register"
tags: ["Table", "Metadata"]
---

# Register a table to a namespace

`POST /v1/table/{id}/register`

Register an existing table at a given storage location as `id`.

## Path parameters

- `id` string, required

## Query parameters

- `delimiter` string

## Request body

- RegisterTableRequest
  - `id` string[]
  - `location` string, required
  - `mode` string — There are two modes when trying to register a table, to differentiate the behavior when a table of the same name already exists. Case insensitive, supports both PascalCase and snake_case. Valid values are: * Create (default): the operation fails with 409. * Overwrite: the existing table registration is replaced with the new registration.
  - `properties` unknown

## Response `200`

Table properties result when registering a table

- RegisterTableResponse
  - `transaction_id` string — Optional transaction identifier
  - `location` 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-12-20** `5d6099d672d3` — 8 breaking, 8 warning, 8 info
  - the `code` response property's min was decreased from `400.00` to `0.00` for the response status `400`
  - the `code` response property's min was decreased from `400.00` to `0.00` for the response status `401`
  - the `code` response property's min was decreased from `400.00` to `0.00` for the response status `403`
  - the `code` response property's min was decreased from `400.00` to `0.00` for the response status `404`
  - …20 more
- **2025-12-11** `62ebe0595c5f` — 3 breaking
  - removed the enum value `CREATE` of the request property `mode`
  - removed the enum value `OVERWRITE` of the request property `mode`
  - the response property `location` became optional for the status `200`
- **2025-12-11** `6ad4337e3849` — 1 info
  - added the optional property `transaction_id` to the response with the `200` status
- **2025-08-01** `6c415039fe56` — 1 info
  - added the new optional request property `mode`
- **2025-07-29** `40a3bc489d46` — 8 breaking, 16 warning, 16 info
  - the response property `type` became optional for the status `400`
  - the response property `type` became optional for the status `401`
  - the response property `type` became optional for the status `403`
  - the response property `type` became optional for the status `404`
  - …36 more

[Full history](https://skmtc.dev/lance-format/apis/lance-namespace-specification/changes/v1/table/:id/register/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/5d6099d672d3/schema)