---
title: "Insert records into a table"
method: POST
path: "/v1/table/{id}/insert"
tags: ["Table", "Data"]
---

# Insert records into a table

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

Insert new records into table `id`.

For tables that have been declared but not yet created on storage
(is_only_declared=true), this operation will create the table with
the provided data.

REST NAMESPACE ONLY
REST namespace uses Arrow IPC stream as the request body.
It passes in the `InsertIntoTableRequest` information in the following way:
- `id`: pass through path parameter of the same name
- `mode`: pass through query parameter of the same name

## Path parameters

- `id` string, required

## Query parameters

- `delimiter` string
- `branch` string
- `mode` string

## Response `200`

Result of inserting records into a table

- InsertIntoTableResponse — Response from inserting records into a table
  - `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.
- `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` — 7 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
  - …3 more
- **2026-06-05** `9932582b6bd7` — 2 info
  - added the new optional `query` request parameter `branch` to all path's operations
  - added the new optional `query` request parameter `branch`
- **2025-12-20** `5d6099d672d3` — 6 breaking, 6 warning, 6 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`
  - …14 more
- **2025-12-11** `62ebe0595c5f` — 3 breaking
  - removed the enum value `append` from the `query` request parameter `mode`
  - removed the enum value `create` from the `query` request parameter `mode`
  - removed the enum value `overwrite` from the `query` request parameter `mode`
- …earlier changes not shown

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