---
title: "Update rows in a table"
method: POST
path: "/v1/table/{id}/update"
tags: ["Table", "Data"]
---

# Update rows in a table

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

Update existing rows in table `id`.

## Path parameters

- `id` string, required

## Query parameters

- `delimiter` string

## Request body

- UpdateTableRequest — Each update consists of a column name and an SQL expression that will be evaluated against the current row's value. Optionally, a predicate can be provided to filter which rows to update.
  - `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[]
  - `predicate` string, nullable — Optional SQL predicate to filter rows for update
  - `updates` array[], required — List of column updates as [column_name, expression] pairs
    - string[]

## Response `200`

Update successful

- UpdateTableResponse
  - `transaction_id` string — Optional transaction identifier
  - `updated_rows` integer, required — Number of rows updated
  - `version` integer, required — The commit version associated with the operation

## 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-01-02** `83f8516f0507` — 1 info
  - added the new optional request property `context`
- **2026-01-01** `c987c26ccb0f` — 1 info
  - added the new optional request property `identity`
- **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** `6ad4337e3849` — 1 info
  - added the optional property `transaction_id` to the response with the `200` status
- **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

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