Execute a workflow. Cannot be executed without a published workflow.
API Key authentication. For all API requests, include your API Key in the Authorization HTTP Header, prefixed with Bearer. Example: Authorization: Bearer {API_KEY}. Strongly recommend storing your API Key on the server-side, not shared or stored on the client-side, to avoid possible API-Key leakage that can lead to serious consequences.
Key-value pairs for workflow input variables. Values for file-type variables should be arrays of file objects with type, transfer_method, and either url or upload_file_id. Refer to the user_input_form field in the Get App Parameters response to discover the variable names and types expected by your app.
User identifier, defined by the developer's rules, must be unique within the application. This identifier scopes data access — workflow runs and files are only visible when queried with the same user value.
Response mode. Use blocking for synchronous responses (Cloudflare timeout is 100 s), or streaming for Server-Sent Events. When omitted, defaults to blocking behavior.
streaming, blocking File list. Suitable when files need to be combined with text for input, available only when the model supports Vision capability. To attach a local file, first upload it via Upload File and use the returned id as upload_file_id with transfer_method: local_file.
Successful response. The content type and structure depend on the response_mode parameter in the request.
response_mode is blocking, returns application/json with a WorkflowBlockingResponse object.response_mode is streaming, returns text/event-stream with a stream of ChunkWorkflowEvent objects.Task ID for the in-progress execution. Use this with Stop Workflow Task to cancel a running workflow. Only valid during execution.
Persistent identifier for this workflow run record. Use this with Get Workflow Run Detail to retrieve results after execution.