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

# Compatibility

> Migrate legacy task paths and response aliases without disrupting existing clients.

GENGEN keeps compatibility routes and fields so existing integrations can migrate gradually.

## Legacy task paths

The following paths remain available:

| Legacy path                 | Canonical path                                   |
| --------------------------- | ------------------------------------------------ |
| `/v1/seedance-2/tasks`      | `/api/gengen/v1/contents/generations/tasks`      |
| `/v1/seedance-2/tasks/{id}` | `/api/gengen/v1/contents/generations/tasks/{id}` |

The collection path supports create and list operations. The task path supports retrieve and delete operations.

<Note>
  Existing clients do not need to change immediately. New integrations should use the canonical GENGEN v1 paths.
</Note>

## Legacy request fields

Provider-native `content[]` bodies and selected snake\_case fields can still be accepted for compatibility. New clients should use:

* `assets` for image, video, and audio inputs.
* `controls` for provider-neutral generation settings.
* `providerOptions` for advanced provider-specific overrides.

## Compatibility response fields

Some responses append legacy aliases after the standard fields:

| Compatibility field     | Standard field   |
| ----------------------- | ---------------- |
| `task_id`               | `id`             |
| `video_url` or `videos` | `outputs.videos` |
| `image_url` or `images` | `outputs.images` |
| `created_at`            | `createdAt`      |
| `updated_at`            | `updatedAt`      |

Do not make new clients depend on compatibility aliases. They are retained to protect existing integrations, not to define the next version of the API.