> ## Documentation Index
> Fetch the complete documentation index at: https://dripart-docs-cms-changelog-node-lifecycle.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Use Recraft V4.1 Pro with Comfy Router

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

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

## Quick start

Create a key at [platform.comfy.org/profile/api-keys](https://platform.comfy.org/profile/api-keys) 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_1_pro`

**Endpoint:** `POST https://api.comfy.org/v2/models/recraft/recraftv4_1_pro`

<CodeGroup>
  ```python Python theme={null}
  from comfy_sdk import Comfy

  # Reads COMFY_API_KEY from the environment. Each call sends a fresh
  # Idempotency-Key and waits up to 10 minutes for the finished result.
  with Comfy() as client:
      result = client.models.run(
          "recraft/recraftv4_1_pro",
          {
              "n": 1,
              "prompt": "A single red maple leaf on a plain white background.",
          },
      )

  print(result)
  ```

  ```typescript TypeScript theme={null}
  import { comfy } from "@comfyorg/sdk";

  // Reads COMFY_API_KEY from the environment. Each call sends a fresh
  // Idempotency-Key and waits up to 10 minutes for the finished result.
  const { data } = await comfy.models.run("recraft/recraftv4_1_pro", {
    n: 1,
    prompt: "A single red maple leaf on a plain white background.",
  });

  console.log(data);
  ```

  ```bash cURL theme={null}
  curl https://api.comfy.org/v2/models/recraft/recraftv4_1_pro \
    -H "X-API-Key: $COMFY_API_KEY" \
    -H "Idempotency-Key: $(uuidgen)" \
    -H "Content-Type: application/json" \
    -d "{\"n\": 1, \"prompt\": \"A single red maple leaf on a plain white background.\"}"
  ```
</CodeGroup>

## Schema

### Input

<ParamField body="controls" type="object">
  The controls for the generated image
</ParamField>

<ParamField body="controls.artistic_level" type="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`
</ParamField>

<ParamField body="controls.background_color" type="object">
  RGB color values
</ParamField>

<ParamField body="controls.background_color.rgb" type="integer[]" required />

<ParamField body="controls.colors" type="object[]">
  An array of preferable colors
</ParamField>

<ParamField body="controls.colors[].rgb" type="integer[]" required />

<ParamField body="controls.no_text" type="boolean">
  Do not embed text layouts
</ParamField>

<ParamField body="model" type="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.
</ParamField>

<ParamField body="n" type="integer">
  The number of images to generate

  Range: `1` to `6`
</ParamField>

<ParamField body="prompt" type="string" required>
  The text prompt describing the image to generate
</ParamField>

<ParamField body="size" type="string">
  The size of the generated image (e.g., "1024x1024")
</ParamField>

<ParamField body="style" type="string">
  The style to apply to the generated image (e.g., "digital\_illustration")
</ParamField>

<ParamField body="style_id" type="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.
</ParamField>

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

### Output

<ResponseField name="created" type="integer" required>
  Unix timestamp when the generation was created
</ResponseField>

<ResponseField name="credits" type="integer" required>
  Number of credits used for the generation
</ResponseField>

<ResponseField name="data" type="object[]" required>
  Array of generated image information
</ResponseField>

<ResponseField name="data[].image_id" type="string">
  Unique identifier for the generated image
</ResponseField>

<ResponseField name="data[].url" type="string">
  URL to access the generated image
</ResponseField>

## Examples

### Input

```json theme={null}
{
  "n": 1,
  "prompt": "A single red maple leaf on a plain white background."
}
```

### Output

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

## Before you ship

The snippets above are the shortest working call. Three things are the same for every model and are documented once on the [Comfy Router headers](/development/comfy-router/headers) page: send an `Idempotency-Key` on every paid call and reuse it when you retry, expect the connection to be held up to Router's 10 minute deadline, and keep `X-Comfy-Request-Id` from every response. The SDKs do all three for you; the cURL tab does none of them. On failure, `X-Comfy-Error-Type` names the bucket, and a `422` means the body failed the model's schema and was never billed.

<CardGroup cols={3}>
  <Card title="Headers" icon="list" href="/development/comfy-router/headers">
    Authentication, idempotency, request IDs, error buckets, retry pacing, spend limits.
  </Card>

  <Card title="Quick Start" icon="rocket" href="/development/comfy-router/quickstart">
    Typed error handling in Python and TypeScript, reading the 422, walking the catalog.
  </Card>

  <Card title="Limitations" icon="triangle-exclamation" href="/development/comfy-router/limitations">
    What Router does not do today, and what to use instead.
  </Card>
</CardGroup>