> ## Documentation Index
> Fetch the complete documentation index at: https://docs.comfy.org/llms.txt
> Use this file to discover all available pages before exploring further.

# Use Seedance 1.0 Lite I2V 250428 with Comfy Router

> Call byteplus/seedance-1-0-lite-i2v-250428 through Comfy Router: endpoint, request shape and the response Router returns.

API Reference for `byteplus/seedance-1-0-lite-i2v-250428`, served by Comfy Router from BytePlus.

## 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:** `byteplus/seedance-1-0-lite-i2v-250428`

**Endpoint:** `POST https://api.comfy.org/v2/models/byteplus/seedance-1-0-lite-i2v-250428`

<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(
          "byteplus/seedance-1-0-lite-i2v-250428",
          {
              # Request fields are the provider's own — see Input below.
          },
      )

  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("byteplus/seedance-1-0-lite-i2v-250428", {
    // Request fields are the provider's own — see Input below.
  });

  console.log(data);
  ```

  ```bash cURL theme={null}
  # Request fields are the provider's own — see Input below.
  curl https://api.comfy.org/v2/models/byteplus/seedance-1-0-lite-i2v-250428 \
    -H "X-API-Key: $COMFY_API_KEY" \
    -H "Idempotency-Key: $(uuidgen)" \
    -H "Content-Type: application/json" \
    -d '{}'
  ```
</CodeGroup>

## Schema

### Input

<Note>
  Router has not published an authored input schema for this model yet: `GET /v2/models/byteplus/seedance-1-0-lite-i2v-250428/openapi.json` returns an open object with `x-comfy-input-schema-authored: false`. Router forwards the body to BytePlus unchanged, so [BytePlus's own API reference](https://docs.byteplus.com/) is authoritative for the request fields, and nothing is validated server side.
</Note>

### Output

<ResponseField name="content" type="object">
  The output after the video generation task is completed, which contains the download URL of the output video and, when BytePlus returns one, the download URL of its last frame. Both `video_url` and `last_frame_url` are RE-HOSTED onto Comfy storage; every other field here is BytePlus's own. Nullable - BytePlus clears the URLs 24 hours after the task, and a succeeded document polled after that can carry `content` absent or null.
</ResponseField>

<ResponseField name="content.last_frame_url" type="string">
  Download URL for the last frame of the generated video, returned when the request set `return_last_frame`. Do not infer the image format from this URL: BytePlus documents the last frame as PNG on the request side, Router re-hosts whatever bytes it is served and types them from the upstream Content-Type or a content sniff, and `image/jpeg` is only the last-resort fallback when both fail. Router re-hosts the last frame onto Comfy storage and rewrites this field, so it is normally a Comfy-signed URL valid for up to 24 hours - signed for 24 hours when minted and replayed from a 23-hour memo, so a later poll can hand back one with as little as an hour left. When the re-host could not be performed the field keeps BytePlus's own URL instead, which BytePlus clears 24 hours after the task. Either way the link expires, so download the frame rather than storing the URL.
</ResponseField>

<ResponseField name="content.output_format" type="string">
  Container format of the generated video (mp4 or mov), when BytePlus nests it inside `content`. Seedance models more commonly return it as a TOP-LEVEL sibling of `content` - see the top-level `output_format` field - and Router reads whichever of the two is present.
</ResponseField>

<ResponseField name="content.video_url" type="string">
  Download URL for the output video. Router re-hosts the video onto Comfy storage and rewrites this field, so it is normally a Comfy-signed URL valid for up to 24 hours - signed for 24 hours when minted and replayed from a 23-hour memo, so a later poll can hand back one with as little as an hour left. When the re-host could not be performed the field keeps BytePlus's own URL instead, which BytePlus clears 24 hours after the task and caps at 100 downloads on some models. Either way the link expires, so download the video rather than storing the URL.
</ResponseField>

<ResponseField name="created_at" type="integer">
  The time when the task was created. The value is a UNIX timestamp in seconds.
</ResponseField>

<ResponseField name="duration" type="number">
  The duration of the generated video in seconds. Declared as a number rather than an integer because BytePlus is not consistent about it - video tasks have been observed returning whole seconds and sibling BytePlus surfaces report fractional durations - so a client must not assume an integral value. BytePlus's own field, returned on succeeded video tasks and forwarded unchanged.
</ResponseField>

<ResponseField name="error" type="object">
  The error information. If the task succeeds, null is returned. If the task fails, the error information is returned.
</ResponseField>

<ResponseField name="error.code" type="string">
  The error code
</ResponseField>

<ResponseField name="error.message" type="string">
  The error message
</ResponseField>

<ResponseField name="id" type="string">
  The ID of the video generation task
</ResponseField>

<ResponseField name="model" type="string">
  The name and version of the model used by the task
</ResponseField>

<ResponseField name="output_format" type="string">
  Container format of the generated video (mp4 or mov), returned at the TOP LEVEL as a sibling of `content` - this is where the Seedance video task query returns it. BytePlus's own field, forwarded unchanged.
</ResponseField>

<ResponseField name="resolution" type="string">
  The resolution of the generated video, for example `1080p`. BytePlus's own field, returned on succeeded video tasks and forwarded unchanged.
</ResponseField>

<ResponseField name="seed" type="integer">
  The generation seed actually used for the task. BytePlus's own field, returned on succeeded video tasks and forwarded unchanged.

  Format: `int64`
</ResponseField>

<ResponseField name="status" type="string">
  The state of the task

  Possible values: `queued`, `running`, `cancelled`, `succeeded`, `failed`, `expired`
</ResponseField>

<ResponseField name="updated_at" type="integer">
  The time when the task was last updated. The value is a UNIX timestamp in seconds.
</ResponseField>

<ResponseField name="usage" type="object">
  The token usage for the request
</ResponseField>

<ResponseField name="usage.completion_tokens" type="integer">
  The number of tokens generated by the model
</ResponseField>

<ResponseField name="usage.total_tokens" type="integer">
  For the video generation model, the number of input tokens is not calculated and defaults to 0. Therefore, total\_tokens = completion\_tokens.
</ResponseField>

## Examples

### Output

```json theme={null}
{
  "content": {
    "last_frame_url": "https://example.invalid/byteplus/seedance-1-0-lite-t2v-250428/last-frame",
    "video_url": "https://example.invalid/byteplus/seedance-1-0-lite-t2v-250428/generated.mp4"
  },
  "created_at": 1767225600,
  "duration": 5,
  "error": null,
  "id": "3f7a1b28-5c0d-4e91-8a6f-1b2c3d4e5f60",
  "model": "seedance-1-0-lite-t2v-250428",
  "output_format": "mp4",
  "resolution": "1080p",
  "seed": 1234567890123,
  "status": "succeeded",
  "updated_at": 1767225730
}
```

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