Note: The Deployment API use the same settings and behavior as the actions available on the web page at Deployments.
Deployment Endpoints
Base URL:https://api.runcomfy.net
| Endpoint | Method | Description |
|---|---|---|
/prod/v2/deployments | POST | Create a deployment |
/prod/v2/deployments/{deployment_id} | GET | Get a deployment |
/prod/v2/deployments/{deployment_id} | PATCH | Update a deployment |
/prod/v2/deployments | GET | List deployments |
/prod/v2/deployments/{deployment_id} | DELETE | Delete a deployment |
Common path parameters
deployment_id: string (UUID). The unique identifier of the deployment resource. Returned when you create a deployment and used for subsequent operations on that deployment.
Common query parameters
includes: repeatable string. Useincludes=readmeand/orincludes=payloadto include extra fields.ids: repeatable string (UUID). Filter to one or more deployment IDs, e.g.?ids=<id1>&ids=<id2>.
Create a Deployment
Request body (JSON)
| Field | Type | Required | Description |
|---|---|---|---|
name | string | Yes | Human-readable name for dashboards/logs. Example: "image-to-video". |
workflow_id | string (UUID) | Yes | The workflow to deploy. Example: "00000000-0000-0000-0000-000000001111". |
workflow_version | string | Yes | The workflow version label or tag. Example: "v1". |
hardware | array of enum strings | Yes | Exactly one SKU. Although the field is an array, only a single value is supported for now. Example: ["AMPERE_48"]. Supplying multiple values (e.g., ["AMPERE_24", "AMPERE_48"]) will be rejected with a validation error. |
min_instances | integer (0–3) | Yes | Minimum instances kept warm (billable even when idle if > 0). |
max_instances | integer (1–10) | Yes | Upper bound for concurrent instances. Must be ≥ min_instances. |
queue_size | integer (≥ 0) | Yes | Target queue length per instance before adding capacity (subject to max_instances). |
keep_warm_duration_in_seconds | integer (≥ 0) | Yes | How long to keep an instance warm after its last job to avoid cold starts. |
Hardware SKUs
Validhardware values:
Scaling Behavior
- If
min_instances > 0, the deployment maintains at leastmin_instanceswarm instances to reduce cold starts, lower latency at higher cost. It will not scale below this floor, and those instances incur charges even when idle. - If
queue_size = 1, when a second request arrives for an instance, the platform may start another instance (up tomax_instances).
Request example
Response example
Payload Explanation
Thepayload object includes key configuration details for the workflow.
workflow_api_json contains the workflow structure in API format. For more details, refer to the documentation at workflow_api.json.
overrides allows for dynamic modifications to workflow inputs. To learn about using overrides, check out using overrides.
object_info_url provides a URL pointing to an object_info.json file, which serves as a schema registry for nodes. For more details, see object_info.json. Here’s an example of the object_info_url field:
Get a Deployment
Request example
Response example
Update a Deployment
Updatable fields
Tip: Set “is_enabled”: false to stop handling new requests (and stop warm capacity). Set it back to true to re-enable.
Request example
Response example
List Deployments
List All Deployments
Get a summary list of all deployments without readme and payload data.Request example
Response example
List All Deployments (Details)
Get all deployments including readme and payload data using query parameters.Extra fields withincludes:Requesting
?includes=payload→ adds apayload(object):{ "workflow_api_json": {}, "overrides": {}, "object_info_url": ""}?includes=readme→ adds areadme(string, Markdown):""- Use both
includes=readme&includes=payloadto get both fields.readmeand/orpayloadcan significantly increase the response size.
Request example
Response example
Note: Thepayloadandreadmefields are only included when using the?includes=payloadand?includes=readmequery parameters respectively.
List deployments by IDs
Filter deployments by specific IDs without readme and payload data.Filter by IDs withids
?ids=<deployment_id>(repeatable) → returns only those deployments
Request example
Response example
List deployments by IDs (Details)
Filter deployments by specific IDs and include readme and payload data.Filter by IDs withincludes:
?ids=<deployment_id>&includes=payload→ addspayloadfor selected IDs?ids=<deployment_id>&includes=readme→ addsreadmefor selected IDs?ids=<id1>&ids=<id2>&includes=readme&includes=payload→ multiple IDs + both fields (ids is repeatable)
Request example
Response example
Note: Thepayloadandreadmefields are only included when using the?includes=payloadand?includes=readmequery parameters respectively.
