---
title: "Trigger an async materialized view refresh"
method: POST
path: "/v1/materialized_view/{id}/refresh"
tags: ["MaterializedView", "Data"]
---

# Trigger an async materialized view refresh

`POST /v1/materialized_view/{id}/refresh`

Trigger an asynchronous refresh job for materialized view `id`.
Returns a job ID for tracking.

## Request body

- RefreshMaterializedViewRequest
  - `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` Context — Arbitrary context as key-value pairs. How to use the context is custom to the specific implementation. On a request, it carries caller-provided context to the implementation. On a response, it carries implementation-provided context back to the caller. REST NAMESPACE ONLY Context entries are mapped to and from HTTP headers using the `header.` prefix: - On a request, any entry whose key starts with `header.` is sent as an HTTP request header with the prefix stripped. For example, the entry `{"header.Authorization": "Bearer abc"}` is sent as the request header `Authorization: Bearer abc`. - On a response, every HTTP response header is returned as an entry whose key is the header name prefixed with `header.`. For example, the response header `x-request-id: abc123` is returned as the entry `{"header.x-request-id": "abc123"}`.
  - `id` string[] — Table identifier path (namespace + table name)
  - `src_version` integer, nullable — Optional source version to refresh from
  - `max_rows_per_fragment` integer, nullable — Optional maximum rows per fragment
  - `concurrency` integer, nullable — Optional concurrency override
  - `intra_applier_concurrency` integer, nullable — Optional intra-applier concurrency override
  - `source_task_size` integer, nullable — Optional number of source row ids per work item during expansion. Bounds per-actor memory for chunker materialized views.
  - `cluster` string, nullable — Optional cluster name (operational override)
  - `output_limit` integer, nullable — Post-trim cap on view row count after expansion. Valid only for chunker materialized views; returns 400 if set on other kinds.
  - `manifest` string, nullable — Optional inline JSON-serialized GenevaManifest. Operational override for this refresh only; does not mutate the view's snapshotted manifest. When omitted, the manifest stored in the view's metadata is used.

## Response `202`

Refresh job accepted

- RefreshMaterializedViewResponse
  - `context` Context — Arbitrary context as key-value pairs. How to use the context is custom to the specific implementation. On a request, it carries caller-provided context to the implementation. On a response, it carries implementation-provided context back to the caller. REST NAMESPACE ONLY Context entries are mapped to and from HTTP headers using the `header.` prefix: - On a request, any entry whose key starts with `header.` is sent as an HTTP request header with the prefix stripped. For example, the entry `{"header.Authorization": "Bearer abc"}` is sent as the request header `Authorization: Bearer abc`. - On a response, every HTTP response header is returned as an entry whose key is the header name prefixed with `header.`. For example, the response header `x-request-id: abc123` is returned as the entry `{"header.x-request-id": "abc123"}`.
  - `job_id` string, required — The job ID for tracking the refresh job

## 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/lancedb/apis/lance-namespace-specification.md) · [All operations](https://skmtc.net/lancedb/apis/lance-namespace-specification/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/lancedb/lance-namespace-specification/revisions/d5b7c114f475/schema)