---
title: "Drop a table"
method: POST
path: "/v1/table/{id}/drop"
tags: ["Table", "Metadata"]
---

# Drop a table

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

Drop table `id` and delete its data.

## Path parameters

- `id` string, required

## Query parameters

- `delimiter` string, nullable — An opaque token that allows pagination for list operations (e.g. ListNamespaces). For an initial request of a list operation, if the implementation cannot return all items in one response, or if there are more items than the page limit specified in the request, the implementation must return a page token in the response, indicating there are more results available. After the initial request, the value of the page token from each response must be used as the page token value for the next request. Caller must interpret either `null`, missing value or empty string value of the page token from the implementation's response as the end of the listing results.

## Request body

- DropTableRequest — If the table and its data can be immediately deleted, return information of the deleted table. Otherwise, return a transaction ID that client can use to track deletion progress.
  - `id` string[]

## Response `200`

Response of DropTable

- DropTableResponse
  - `id` string[]
  - `location` string
  - `properties` unknown
  - `transactionId` string[] — If present, indicating the operation is long running and should be tracked using GetTransaction

## 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.

## Changes

- **2025-07-29** `40a3bc489d46` — 6 breaking, 12 warning, 12 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`
  - …26 more
- **2025-07-25** `8769f8e36bc4` — 1 breaking, 4 warning, 2 info
  - the `transactionId` response's property type/format changed from `string`/`` to `array`/`` for status `200`
  - removed the request property `name`
  - removed the request property `namespace`
  - removed the optional property `name` from the response with the `200` status
  - …3 more
- **2025-07-21** `db7569410aa4` — 1 info
  - api tag `Metadata` added
- **2025-07-21** `6790486d1fac` — 7 breaking, 15 warning, 23 info
  - added required request body
  - removed the required property `code` from the response with the `400` status
  - removed the required property `code` from the response with the `401` status
  - removed the required property `code` from the response with the `403` status
  - …41 more

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