Skip to main content

Search

Publishing a Workflow as an Endpoint


Introduction

Publishing Workflows as API endpoints lets you build custom generative pipelines in the Web App and deploy them with a single click — no infrastructure setup or model orchestration required.

Creative teams can build and test pipelines visually. Developers get a clean endpoint to integrate. 

To get started, your Developer Portal and Web App accounts must be linked.

 

Step 1 — Publishing a Workflow from the Web App

These steps take place from your Enterprise Workspace in the Web App, and can be completed by admins and editors:

  1. Navigate to the Workflow you want to publish as an API endpoint
  2. In the top-right corner, click Publish
  3. Select Publish new endpoint
  4. In the pop-up, create labels for the inputs and outputs in your Workflow
  5. Click the eye icon to show or hide inputs or outputs from the endpoint view
  6. Click Publish Endpoint

 

Step 2 — Accessing the Workflow from the Developer Portal

These steps take place in the Developer Portal. An admin can share an invite if you don't have access to your organization's Developer Portal account.

  1. Log in to your API account at dev.runwayml.com
  2. Navigate to the menu bar on the top of the page and select Workflows
  3. Select the published Workflow
  4. Modify the inputs and press Run 
  5. 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 use this feature?

Enterprise plans with linked Web App and Developer Portal accounts. 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?

Anything that benefits from a custom generative pipeline — client-facing apps, internal tools, automated content workflows, and more. If you can build it as a Workflow, you can ship it as an API.