Use Recraft V4 with Comfy Router

Call recraft/recraftv4 through Comfy Router: endpoint, request shape and the response Router returns.

API Reference for recraft/recraftv4, served by Comfy Router from Recraft.

Quick start

Create a key in your Comfy workspace and export it as COMFY_API_KEY. The Python and TypeScript snippets use the Comfy SDKs (pip install comfy-sdk, npm install @comfyorg/sdk); the cURL snippet is the same call over raw HTTP.

Model ID: recraft/recraftv4

Endpoint: POST https://api.comfy.org/v2/models/recraft/recraftv4

Python

from comfy_sdk import Comfy

# Reads COMFY_API_KEY from the environment.
# The SDK automatically creates an idempotency key and reuses it for automatic retries.
with Comfy() as client:
    result = client.models.run(
        "recraft/recraftv4",
        {
            "n": 1,
            "prompt": "A single red maple leaf on a plain white background.",
        },
    )

print(result)

Schema

Input

controls · object

The controls for the generated image

controls.artistic_level · integer

Defines artistic tone of your image. At a simple level, the person looks straight at the camera in a static and clean style. Dynamic and eccentric levels introduce movement and creativity.

Range: 0 to 5

controls.background_color · object

RGB color values

controls.background_color.rgb · integer[] · required

controls.colors · object[]

An array of preferable colors

controls.colors[].rgb · integer[] · required

controls.no_text · boolean

Do not embed text layouts

model · string

The model to use for generation (e.g., “recraftv3”). This field is NOT constrained to an enum: the proxy forwards whatever the caller sends. The spellings Comfy ships — the set Comfy Router addresses as recraft/<model> — are recraftv2, recraftv3, recraftv4, recraftv4_pro, recraftv4_1, recraftv4_1_utility, recraftv4_1_pro, recraftv4_1_utility_pro, recraftv4_styles, recraftv4_styles_pro, recraftv4_1_vector, recraftv4_1_utility_vector, recraftv4_1_pro_vector, recraftv4_1_utility_pro_vector, recraftv4_styles_vector and recraftv4_styles_pro_vector. They are written out here rather than named by reference because the RecraftGenerationModel component that declares them is $ref-ed by nothing and is therefore pruned from the spec served at GET /openapi, so a pointer to it would dangle in the served document. The four recraftv4_styles* spellings additionally require style_id — see that field.

n · integer

The number of images to generate

Range: 1 to 6

prompt · string · required

The text prompt describing the image to generate

size · string

The size of the generated image (e.g., “1024x1024”)

style · string

The style to apply to the generated image (e.g., “digital_illustration”)

style_id · string

The style ID to apply to the generated image (e.g., “123e4567-e89b-12d3-a456-426614174000”). If style_id is provided, style should not be provided. REQUIRED by the four recraftv4_styles* models: Recraft rejects those without a style_id or style reference. Mint one with POST /proxy/recraft/styles, which this same proxy serves under the same credentials. Nothing on this route enforces the pairing — the body is forwarded to Recraft unchanged, so a recraftv4_styles* call without it reaches the partner and comes back 4xx.

Generated from the schema Router serves at GET /v2/models/recraft/recraftv4/openapi.json, the same document it validates a call against before the request reaches the provider.

Output

created · integer · required

Unix timestamp when the generation was created

credits · integer · required

Number of credits used for the generation

data · object[] · required

Array of generated image information

data[].image_id · string

Unique identifier for the generated image

data[].url · string

URL to access the generated image

Examples

Input

{
  "n": 1,
  "prompt": "A single red maple leaf on a plain white background."
}

Output

{
  "created": 1767225600,
  "credits": 1,
  "data": [
    {
      "image_id": "3f7a1b28-5c0d-4e91-8a6f-1b2c3d4e5f60",
      "url": "https://example.invalid/recraft/recraftv3/generated.png"
    }
  ]
}

Before you ship

The SDKs create an Idempotency-Key and reuse it for automatic retries. For manual retries, reuse the original key. Router can hold the connection for up to 10 minutes.

When a request fails, Router sends an X-Comfy-Error-Type response header explaining why. A 422 means Router rejected the input before calling the provider. Download generated assets promptly because result URLs can expire.

Headers

Authentication, idempotency, request IDs, error buckets, retry pacing, spend limits.

Using the Router API

Model discovery, validation errors, retries, and billing.

Limitations

What Router does not do today, and what to use instead.