Skip to main content

Run pipeline

POST 
/platform/pipeline/execute

Trigger immediate execution rather than waiting for the cron schedule. Identify the pipeline using pipeline_id, then monitor pipeline runs. Read run identifiers from actual responses/history rather than assuming one fixed format.

Contract caveat​

Source examples send only pipeline_id and say Maestro injects customer_id. The imported ExecutePipelinePayload requires both. Deployed behavior has not been verified; authenticated tenant context must not be confused with arbitrary caller-selected identity. The source describes paused-pipeline failures as 400, whereas the imported responses document 403 for an invalid execution state and 404 for a missing or unready pipeline. Do not rely on the source-only code. Use Unpause pipeline when scheduled processing should resume.

Request​

Responses​

Pipeline execution triggered