Create Data Product
Produce a data product from a finished pipeline run and rebuild its review queue. The data product is where extracted rows are read and review holdback is enforced.
Produce a data product from a finished pipeline run. The data product is the read surface for the run's extracted rows: you read its rows, generate a share token, and export CSV through the data-products endpoints. It is also where per-cell review holdback lives. Fields a blocking gate parked for review surface with status only, with the value withheld, until a reviewer resolves them.
A pipeline is effectively one-to-one with its data product. Calling this endpoint again reactivates the existing product rather than minting a duplicate, and in either case it rebuilds the review queue from the run's stored validation verdicts. The run must have at least one completed (or partial) document; a run with nothing processed yet is rejected with 400. Preview runs cannot produce data products.
The response carries the created (or reactivated) data product and its auto-generated share token. Pass an optional name to label the product; it defaults to the run name plus a suffix. Once created, use the returned data_product id with the data-products endpoints to read rows and the share token for the public delivery surface. This endpoint requires an API key with the write scope.
/v1/pipelines/{id}/data-productResponse
Response fields
Response
{
"dataProduct": {
"id": "dp_uuid_1",
"name": "Lease Agreement — Data Product",
"pipeline_id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
"status": "active"
},
"shareToken": {
"data_product_id": "dp_uuid_1",
"token": "shr_8f2c1a9b3d7e4f60"
}
}Errors
Error responses