v1
latestOpenAPI 3.1.02026-07-22106199311.5 KBPipeline Execution
Execute Published Pipeline
Triggers the asynchronous execution of a named, published pipeline within the specified project.
The pipeline must be published to the target environment before it can be executed. On success, returns a pipelineExecutionId that can be used to track or query the execution status.
Key behaviours:
- By default, the latest published version of the pipeline is executed. Use versionName to target a specific artifact version.
- If no agentId is provided, the default agent configured for the target environment is used.
- Use executionTag to control concurrency — only one execution per tag is permitted to run at a time within a given environment. A 409 Conflict is returned if an execution with the same tag is already in progress.
- Runtime variable values can be overridden per-execution using scalarVariables (key-value pairs) or gridVariables (two-dimensional string arrays), without modifying the published pipeline definition.
- A 410 Gone is returned if the pipeline has been disabled.
post/v1/projects/{projectId}/pipeline-executions
Path parameters
projectIdstring uuid required
Request body
Example request
{
"agentId": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
"environmentName": "Dev Env",
"executionTag": "tag1",
"pipelineName": "My pipeline",
"versionName": "1.1.0"
}Response
Pipeline executed
Example response
{
"pipelineExecutionId": "1398aa31-af57-4a6a-9752-27c2e8556c3f"
}