Skip to main content
GENGEN keeps compatibility routes and fields so existing integrations can migrate gradually.

​
Legacy task paths

The following paths remain available: The collection path supports create and list operations. The task path supports retrieve and delete operations.
Existing clients do not need to change immediately. New integrations should use the canonical GENGEN v1 paths.

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