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

# API reference

> Conventions shared by GENGEN v1 endpoints.

## Base URL

```text theme={"dark"}
https://gengen.farm/api/gengen/v1
```

All endpoint paths in this reference are relative to that base URL.

## Authentication

Send a GENGEN API key as a bearer token:

```http theme={"dark"}
Authorization: Bearer gengen_live_xxxxxxxxxxxxxxxx
```

See [Authentication](/authentication) for key creation and storage guidance.

## Request conventions

New generation requests use camelCase fields and this top-level order:

```json theme={"dark"}
{
  "model": "public-model-id",
  "mode": "optional-operation-mode",
  "prompt": "Creative text instruction",
  "assets": {},
  "controls": {},
  "providerOptions": {}
}
```

## Response conventions

Generation responses expose standard fields first:

```json theme={"dark"}
{
  "id": "provider:public-task-id",
  "model": "public-model-id",
  "status": "pending",
  "outputs": {
    "videos": [],
    "images": []
  }
}
```

Use `outputs.videos` and `outputs.images` for generated media. Fields such as `task_id`, `video_url`, `created_at`, and provider-native containers are compatibility-only.

<Note>
  The list-tasks endpoint currently returns its persisted list items with snake\_case timestamps and Unix seconds. Its endpoint schema documents the current behavior rather than a future normalized shape.
</Note>

## API examples

The embedded API playground can execute requests against production endpoints. Add a valid GENGEN bearer token and review the request before sending it; successful billable requests may charge your wallet. The guided [API Explorer](https://gengen.farm/api-explorer) remains available for complete upload and task workflows.