Trigger pipeline execution
POST /pipelines/{pipelineId}/trigger
Authorizations
Section titled “Authorizations ”Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ”Unique identifier of the pipeline to retrieve
Unique identifier of the pipeline to retrieve
Request Body
Section titled “Request Body ”object
Runtime input data for the pipeline execution
object
Map of file slot IDs to file ID(s) - array if multiple: true
object
A unique nanoid for the resource (for more information please see: https://zelark.github.io/nano-id-cc/)
Map of dataset slot IDs to table ID(s) - array if multiple: true
object
A unique nanoid for the resource (for more information please see: https://zelark.github.io/nano-id-cc/)
Map of data input slot IDs to their values
object
Responses
Section titled “ Responses ”Pipeline execution triggered successfully. For streaming pipelines (streaming_language_model), poll GET /pipeline-executions/:executionId to retrieve handlerOutput.streamingChannelId before subscribing to the SSE stream.
object
Unique identifier for the created execution
Initial status of the execution (typically ‘pending’)
When the execution was created (ISO 8601)
Bad Request - Validation error or invalid input
object
Unauthorized - Authentication required or invalid token
object
Forbidden - Insufficient permissions
object
Not Found - Resource does not exist
object
Conflict - Resource already exists or operation conflicts with current state