Enriching Captures - Extralt Docs

Enrich processes Captures from one Extract Run and writes one normalized Item for each successfully processed Capture. Use it when you need a consistent English-language product record, taxonomy, attributes, signals, normalized options, identifiers, or structured embedded SKU data.

Before you start

You need a Run with Captures. Choose an explicit Enrichment budget: the maximum number of Captures to process. Enrich consumes one credit per processed Capture.

An Item remains a page-grain record with lineage to its Capture. Enrich does not publish final Products, Variants, Listings, Offers, Reviews, or Stores. Extend performs that downstream work.

Start an Enrichment

Dashboard: open Enrich > Enrichments, create a new Enrichment, choose the source Run, and set the budget. You can also enable auto_enrich when creating an Extract Run; the system still creates Enrich as a separate dependent job.

API:

curl -s -X POST "https://api.extralt.com/v0/enrich/enrichments" \
  -H "Authorization: Bearer $EXTRALT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "extract_run_id": "your-run-id",
    "budget": 100
  }' | jq

Use the generated OpenAPI reference as the source of truth for the current request and response schema.

Monitor and stop work

The Enrichment list and detail views expose source Run, lifecycle status, processed count, errors, and budget. An active Enrichment can be stopped from the dashboard or API.

Inspect Items

Browse Items under Enrich > Items. The list can be scoped to an Enrichment; the detail view preserves Capture, Run, source URL, and observation lineage.

The API supports paginated Item listing and Item detail. See the OpenAPI reference for current filters and response fields.

For analytical questions over Items, use the dashboard AI query view, the dashboard agent, or the constrained SQL endpoint. Results from the SQL endpoint are capped at 100 rows.

What an Item contains

An Item contains normalized product content, taxonomy ids and path, attributes, signals, image text, option axes, selected media, source SKUs and identifiers, review aggregates, country, Store key, source URL, and processing lineage.

See items for field semantics.