Skip to main content

Materialize

Trigger materialization backfill for filter indexes. Rebuilds the materialized field value index used by filter queries after bulk ingestion.

The POST /v1/search/materialize endpoint triggers a rebuild of the materialized field value index: the pre-computed store of extracted field values that gives filter, autocomplete, and field-value queries sub-second response times even on large workspaces. Run it after bulk document ingestion or schema changes to ensure filter results are current.

Materialization can be resource-intensive on large workspaces. Avoid calling this endpoint during peak usage. For incremental ingestion, the index updates automatically per document.
POST/v1/search/materialize

Request

Response

Response fields

statusstring`complete` when the backfill finishes.
messagestringHuman-readable confirmation.
processedintegerNumber of documents materialized during the backfill.

Response

{
  "status": "complete",
  "message": "Materialization triggered for all documents.",
  "processed": 1842
}

Errors

Error responses

401unauthorizedMissing or invalid API key.
429rate_limitedToo many requests. Retry after the period indicated in the Retry-After header.

In a typical bulk-ingestion workflow, call POST /v1/extract for each file, wait for all extraction.complete webhooks, then trigger POST /v1/search/materialize once. After the backfill completes, all filter and omnisearch endpoints will reflect the newly ingested data.

Related

Filter Documents
Materialized Index