Create a materialization
Creates a materialization and starts building. Behavior depends on the request body (see CreateMaterializationRequest):
- Orchestrated build — supply
buildInstructions. The publisher builds directly into the caller-assigned names derived from the package’s already-compiled build plan (read offPackage.buildPlan). Returns the materialization already building. - Auto-run (standalone, default) — omit
buildInstructions; the publisher self-assigns names and runs all phases in one pass.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
Name of the environment
Name of the package
Body
Options for starting a materialization. Two modes — (1) auto-run (default), omit buildInstructions and the publisher self-assigns names and runs all phases in one pass; (2) orchestrated build, supply buildInstructions and the publisher builds directly into the caller-assigned names from the package's already-compiled build plan (read off Package.buildPlan).
Orchestrated build. When present, the publisher creates the materialization already building these caller-assigned sources (table id, physical name, realization) into the exact names provided — the caller derived these instructions from Package.buildPlan up front. Omit for auto-run (the publisher self-assigns names and builds all persist sources).
Build a new table even when a source's sourceEntityId is unchanged.
Restrict the plan/build to these persist source names. Omit = all persist sources.
Response
Materialization created
A record of one materialization run for a package.
Phase-aware status of a materialization run.
PENDING, MANIFEST_ROWS_READY, MANIFEST_FILE_READY, FAILED, CANCELLED Build output. Null until status = MANIFEST_FILE_READY.
Error message if the materialization failed
Materialization metadata including build options, source counts, and durations