Skip to main content
POST
Create a materialization

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

environmentName
string
required

Name of the environment

packageName
string
required

Name of the package

Body

application/json

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).

buildInstructions
object | null

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).

forceRefresh
boolean
default:false

Build a new table even when a source's sourceEntityId is unchanged.

sourceNames
string[]

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.

id
string
environmentId
string
packageName
string
status
enum<string>

Phase-aware status of a materialization run.

Available options:
PENDING,
MANIFEST_ROWS_READY,
MANIFEST_FILE_READY,
FAILED,
CANCELLED
manifest
object | null

Build output. Null until status = MANIFEST_FILE_READY.

startedAt
string<date-time> | null
completedAt
string<date-time> | null
error
string | null

Error message if the materialization failed

metadata
object | null

Materialization metadata including build options, source counts, and durations

createdAt
string<date-time>
updatedAt
string<date-time>