---
title: "Update per-field metadata"
method: POST
path: "/v1/table/{id}/update_field_metadata"
tags: ["Table", "Metadata"]
---

# Update per-field metadata

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

Update the Arrow field (column) metadata for table `id`.

Each entry targets a field by `path` and merges the provided key-value
pairs into that field's existing metadata, or replaces it when `replace`
is true. A null metadata value deletes that key.

## Path parameters

- `id` string, required

## Query parameters

- `delimiter` string

## Request body

- UpdateFieldMetadataRequest
  - `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[] — Table identifier path (namespace + table name)
  - `branch` string — Branch to target. When not specified, the main branch is used.
  - `updates` UpdateFieldMetadataEntry[], required — List of per-field metadata updates to apply
    - `path` string, required — Lance field path whose metadata to update. Nested fields use dot-separated segments; use backtick-quoted segments for literal dots and double backticks inside quoted segments. Use canonical full paths for display and errors; leaf names alone only identify top-level fields; invalid or unresolved paths should return InvalidInput or TableColumnNotFound.
    - `metadata` unknown, required
    - `replace` boolean, nullable — If true, replace the field's existing metadata entirely; otherwise merge into it (optional, defaults to false).

## Response `200`

Field metadata update result

- UpdateFieldMetadataResponse
  - `context` unknown
  - `version` integer, required — The commit version associated with the operation
  - `fields` 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.
- `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.

---

[API](https://skmtc.net/lance-format/apis/lance-namespace-specification.md) · [All operations](https://skmtc.net/lance-format/apis/lance-namespace-specification/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/lance-format/lance-namespace-specification/versions/f09656f7f568/schema)