Skip to main content
The Platform API is organized into eight resource categories. Every endpoint lives under https://api.runflow.io and uses Authorization: Bearer <token> for auth — see Introduction for the stability contract and how to get access. Expand a category below to see what it covers, then jump into the full reference with parameters, schemas, and a live “Try it” playground.

Runs — 17 operations

A run is an execution of a flow or pipeline. Use these endpoints to search run history, inspect per-node logs, check status, and redeliver webhook callbacks that failed.Open Runs reference →What’s inside
  • Core — GET /v1/runs, GET /v1/runs/{id}, PATCH /v1/runs/{id}
  • Logs & node runs — search and fetch individual logs or per-node execution records
  • Callback redelivery — inspect callback history and redeliver failed webhooks
  • Enum catalogs — statuses, sources, target types, log levels
Assets are images you’ve uploaded to Runflow. They can be organized into folders and uploaded via presigned URLs for large files.Open Assets reference →What’s inside
  • Core — search, get, and delete assets under /v1/assets
  • Upload flow — three-step presigned S3 dance via /v1/asset-uploads and confirmations
  • Folders — CRUD under /v1/asset-folders
  • Enum catalogs — source types, asset types
Webhooks are HTTPS endpoints in your system that Runflow POSTs to when events happen. Pair them with callback secrets to verify payload authenticity.Open Webhooks reference →What’s inside
  • Subscriptions — full CRUD under /v1/webhooks
  • Delivery history — inspect delivery chains and per-attempt details
  • Callback secrets — HMAC signing key management under /v1/callback-secrets
  • Enum catalog — webhook event types
Flows are the core graph primitive in Runflow — directed graphs of nodes that define how inputs become outputs. Use these endpoints to author flows programmatically, manage their inputs and outputs, and work with reusable templates.Open Flows reference →What’s inside
  • Flow CRUD — GET/POST/PATCH/DELETE /v1/flows, lookup by owner & slug
  • Flow graph — replace a flow’s entire graph in one call
  • Flow inputs & outputs — CRUD for each input and output parameter
  • Flow nodes — create, update, delete individual nodes in a flow
  • Flow node inputs & outputs — per-node parameter management
  • Flow templates — reusable flow blueprints under /v1/flow-templates
  • Flow summaries — read-only lightweight listing
  • Flow runs — list runs triggered from a specific flow
  • Enum catalogs — flow types, statuses, visibilities, categories, node execution states, node types
The model catalog — browse the AI models Runflow can run, their creators, families, pricing, and example inputs/outputs. Mostly read-only metadata with a couple of mutation endpoints for dispatching runs.Open Models reference →What’s inside
  • Model catalog — search, get, and look up models by owner and slug
  • Model runs — create and dispatch a model run directly
  • Model examples — gallery entries per model
  • Model inputs & outputs — parameter metadata
  • Model pricing — per-model customer pricing
  • Model FAQ & related links — documentation metadata
  • Model creators & families — catalog of who built what
  • Model stats — aggregate statistics for public models
  • Enum catalogs — model statuses, availability, categories, license types
ComfyUI workflows are a specialized kind of flow backed by ComfyUI. This category covers the workflow catalog, per-workflow inputs/outputs, and the library of built-in nodes available to workflow authors.Open ComfyUI reference →What’s inside
  • Workflow CRUD — /v1/comfyui-workflows and lookup by owner & slug
  • Workflow inputs & outputs — per-workflow parameter management
  • Workflow runs — list runs triggered from a specific workflow
  • Built-in nodes — catalog of nodes available in ComfyUI under /v1/builtin-nodes
  • Enum catalog — flow categories
Solutions bundle flows, models, and ComfyUI workflows into higher-level integration surfaces — pre-built products that customers can drop into their stack.Open Solutions reference →What’s inside
  • Solutions — search, get individual solutions
  • Solution sections — structured content blocks
  • Bundled resources — list and fetch the flows, models, and ComfyUI workflows attached to a solution
  • Enum catalog — flow categories
Small enum and lookup catalogs referenced by other resources. All are read-only and safe to fetch without auth scope concerns. Useful when you need the full set of valid values for a pricing, variable, or model field.Open Catalogs reference →What’s inside
  • Pricing catalogs — dimensions, model types, rule effects, units
  • Variable catalogs — behaviours, types, validators
Every catalog exposes a list and a get by id endpoint.