Use Happyhorse 1.0 R2V with Comfy Router

API Reference for wan/happyhorse-1.0-r2v, served by Comfy Router from Wan.

Quick start

Create a key at 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: wan/happyhorse-1.0-r2v Endpoint: POST https://api.comfy.org/v2/models/wan/happyhorse-1.0-r2v

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(
        "wan/happyhorse-1.0-r2v",
        {
            # Request fields are the provider's own — see Input below.
        },
    )

print(result)

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("wan/happyhorse-1.0-r2v", {
  // Request fields are the provider's own — see Input below.
});

console.log(data);

# Request fields are the provider's own — see Input below.
curl https://api.comfy.org/v2/models/wan/happyhorse-1.0-r2v \
  -H "X-API-Key: $COMFY_API_KEY" \
  -H "Idempotency-Key: $(uuidgen)" \
  -H "Content-Type: application/json" \
  -d '{}'

Schema

Input

Router has not published an authored input schema for this model yet: GET /v2/models/wan/happyhorse-1.0-r2v/openapi.json returns an open object with x-comfy-input-schema-authored: false. Router forwards the body to Wan unchanged, so Wan’s own API documentation is authoritative for the request fields, and nothing is validated server side.

Output

object

required

string

Actual prompt after intelligent rewriting (for video tasks)

string

Audio URL for I2V tasks with audio generation

string

The error code for the failed request (not returned if request is successful)

string

Task completion time

string

Detailed information about the failed request (not returned if request is successful)

string

Original input prompt (for video tasks)

object[]

List of task results for image generation tasks

string

Actual prompt after intelligent rewriting (if enabled)

string

Image error code (returned when some tasks fail)

string

Image error information (returned when some tasks fail)

string

Original input prompt

string

Generated image URL address

string

Task execution time

string

Task submission time

string

required

Task ID

object

Task result statistics for image generation tasks

integer

Number of failed tasks

integer

Number of successful tasks

integer

Total number of tasks

string

required

Task statusPossible values: PENDING, RUNNING, SUCCEEDED, FAILED, CANCELED, UNKNOWN

string

Video URL for completed video generation tasks. Link validity period 24 hours

string

required

Unique request identifier

object

Output information statistics. Only successful results are counted

integer

Video resolution level (I2V and wan3.0-video tasks)

number

Duration of generated video in seconds (I2V and wan3.0-video tasks)

integer

Frame rate of the generated video (wan3.0-video tasks)

integer

Number of generated images (T2I tasks)

number

Duration of the input video in seconds, 0.0 when no video input (wan3.0-video tasks)

number

Duration of the output video in seconds (wan3.0-video tasks)

string

Aspect ratio of the generated video, e.g. 16:9 (wan3.0-video tasks)

string

Image resolution (T2I tasks)

integer

Number of generated videos (T2V tasks)

number

Duration of generated video in seconds (T2V tasks)

string

Video resolution ratio (T2V tasks)

string

Error code for a failed request, reported at the ROOT of the envelope rather than under output (not returned if the request succeeded).

string

Detailed information about a failed request, reported at the ROOT of the envelope rather than under output (not returned if the request succeeded). Read this before falling back to output.message.

Examples

Output

{
  "output": {
    "actual_prompt": "a single red maple leaf falling onto still water, slow motion, shallow depth of field",
    "end_time": "2027-01-01T00:01:04.000Z",
    "orig_prompt": "a single red maple leaf falling onto still water",
    "scheduled_time": "2027-01-01T00:00:01.000Z",
    "submit_time": "2027-01-01T00:00:00.000Z",
    "task_id": "0385dc79-5ff8-4d82-bcb6-7c1a9f2e4d60",
    "task_status": "SUCCEEDED",
    "video_url": "https://example.invalid/wan/wan3.0-video/generated.mp4"
  },
  "request_id": "7574ee8f-38a3-4b1e-9280-11c33ab46e51",
  "usage": {
    "SR": 720,
    "duration": 5
  }
}

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 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.

Headers

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

Quick Start

Typed error handling in Python and TypeScript, reading the 422, walking the catalog.

Limitations

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

Develop with Comfy

Deploy ComfyUI

Run Workflows

Comfy Router

Comfy CLI

Specifications

Use Happyhorse 1.0 R2V with Comfy Router

Quick start

Schema

Input

Output

Examples

Output

Before you ship

Headers

Quick Start

Limitations

​Quick start

​Schema

​Input

​Output

​Examples

​Output

​Before you ship

Headers

Quick Start

Limitations

Quick start

Schema

Input

Output

Examples

Output

Before you ship