Endpoints
Run
Trigger a Runchat workflow by ID. Pass inputs by parameter ID, or post a JSON body that flows into the workflow’s webhook node.
POST
This endpoint runs a workflow that already exists. To build or edit a
workflow programmatically, the MCP server or
CLI are usually the easiest path — they expose
the full canvas toolset (create nodes, connect, run, publish) as native tools
and handle auth. The same tools are also available over plain HTTP via the
Canvas API.
Authorizations
Bearer token authentication using Runchat API key. API keys can be created from the account menu
Path Parameters
The unique identifier for the Runchat flow.
Body
application/json
Input data for the Runchat execution. Provide runchat_instance_id to continue an existing execution. The inputs object structure should match the parameters defined in the Runchat API schema, keyed by paramId_nodeId. Alternatively, send raw data for webhook-triggered flows.
Request body for executing a Runchat flow.
Response
Successful execution of the Runchat flow.