Skip to main content
ComfyUI offers several API options depending on where you want to run your workflows and how much infrastructure you want to manage. This page helps you choose the right approach.

​
Start Here

For a new integration, use the Comfy SDKs and the Comfy API v2 they call. v2 is a new, versioned HTTP interface. It coexists with the existing Cloud API and ComfyUI Server API. See the Comfy API v2 Overview. The same code runs against Comfy Cloud, a serverless deployment, and your own machine.

Comfy SDKs

Official Python and TypeScript SDKs for running workflows from your own application. Currently in beta.
The other APIs below are still fully supported, and they cover surface the SDKs do not reach yet. Nothing here is deprecated.

​
Which API Should I Use?

All of them use the same workflow format (API format), so you can develop and test workflows locally and move them to the cloud without changes.

​
Getting Started

Comfy SDKs

Run workflows from Python or TypeScript, against Cloud or your own machine.

Cloud API

Run workflows on Comfy’s managed infrastructure. No GPU setup required.

ComfyUI Server API

Run ComfyUI as a server on your own machine and call it via API.

Partner Node API Integration

Use paid Partner Nodes in headless or API-driven workflows.

​
Prerequisites

Before using any API, you’ll need:
  • An API key for anything that touches Comfy Cloud or Partner Nodes (see Getting an API Key). A purely local ComfyUI does not need one.