Comfy APIs: an overview
Last updated: June 12, 2026
This article explains the different APIs available across Comfy.
Q. What APIs does Comfy provide?
Comfy provides different APIs depending on your use case:
Local Server API → Run workflows through your own ComfyUI instance
Cloud API → Run workflows on Comfy-managed infrastructure
Registry API → Publish and manage custom nodes
Q. Which API should I use?
Choose based on what you're building:
Self-hosting / custom frontend / backend integration → Local Server API
Managed infrastructure / no local GPU → Cloud API
Publishing custom nodes → Registry API
Q. Can I run workflows through the Cloud API?
Yes.
Cloud API allows you to submit workflows and receive results without managing local GPUs.
Please note:
Cloud API requires a supported Comfy Cloud subscription
Cloud usage consumes Comfy Credits
Cloud API functionality may evolve over time
For details:
👉 See Comfy Docs - Development for Cloud
Q. Can I run Partner Nodes through APIs?
Yes.
Workflows using Partner Nodes require authentication when called programmatically.
For implementation details and API references:
👉 See Comfy Docs - Cloud API References
👉 See Comfy Docs - Partner Nodes
Q. Where can I learn more?
Developer overview → https://docs.comfy.org/development/overview
Local Servicer API → https://docs.comfy.org/development/comfyui-server/comms_overview
Cloud API reference → https://docs.comfy.org/development/cloud/api-reference
Registry overview & API → https://docs.comfy.org/registry/overview
Building custom nodes → https://docs.comfy.org/custom-nodes/overview