Introduction
Publishing a Workflow as an API endpoint lets you build a custom generative pipeline in the Web App and deploy it with a single click.
Creative teams can build and test pipelines visually, and developers get a clean endpoint to integrate.
To publish a Workflow as an endpoint, your Developer Portal and Web App accounts must be linked.
Step 1 — Publishing a Workflow from the Web App
Publishing a Workflow as an endpoint takes place from your Workspace in the Web App, and can be completed by admins and editors. Six steps, in order:
- Navigate to the Workflow you want to publish as an API endpoint
- In the top-right corner, click Publish
- Select Publish new endpoint
- In the pop-up, create labels for the inputs and outputs in your Workflow
- Click the eye icon to show or hide inputs or outputs from the endpoint view
- Click Publish Endpoint
Step 2 — Accessing the Workflow from the Developer Portal
Accessing a Workflow published as an endpoint takes place in the Developer Portal. An admin can share an invite if you don't have access to your organization's Developer Portal account.
- Log in to your API account at dev.runway.com
- Navigate to the menu bar on the top of the page and select Workflows
- Select the published Workflow
- Modify the inputs and press Run
- Alternatively, click Get Code to call the Workflow as an endpoint
Next steps
With your Workflow published as an API endpoint, you can instantly deploy custom sites, applications, and integrations powered by your customized Runway Workflows.
As your needs evolve, you can publish additional Workflows as separate endpoints or update existing ones — each change deploys immediately without any additional setup.
FAQ
Who can publish a Workflow as an endpoint?
Plans with linked Web App and Developer Portal accounts. On workspaces with multiple members, Admins and editors can publish endpoints; developers can access and integrate them.
Will the endpoint use Web App or Developer credit balances?
Endpoints use credits from your Developer account. Running the same Workflow directly in the Web App will still use the Web App credits.
Do I need to write code to build a Workflow?
No. Workflows are built visually in the Web App. Developers only need to touch code when integrating the published endpoint.
What kinds of things can I build with this?
Publishing a Workflow as an endpoint supports anything that benefits from a custom generative pipeline: client-facing apps, internal tools, automated content workflows, and more. A Workflow you can build in the Web App can be published as an API endpoint.