OpenAPI generators.yml reference

Path to the OpenAPI specification file.

URL of the API definition origin for pulling updates. For instructions on how to set up automatic syncing, refer to Sync your OpenAPI specification.

Path to OpenAPI overrides file.

Namespace for the specification. Useful for configuring a single package with multiple API versions.

OpenAPI-specific generation settings.

Whether to use the titles of schemas within an OpenAPI definition as the names of types within Fern.

Whether to include path parameters within the generated in-lined request.

Whether to inline allOf schemas during code generation. When true, Fern recursively visits allOf schema definitions and inlines them into the child schema. When false, allOf schemas are extended through inheritance.

Enabling this setting allows child schemas to override parent property requirements. For example, a child schema can mark a parent’s required property as optional. Without this setting, Fern ignores the child schema’s optional declaration and preserves the parent schema’s requirement instead.

Whether to prefer undiscriminated unions with literals.

Whether to only include schemas referenced by endpoints in the generated SDK (tree-shaking).

Preserves nullable schemas in API definition settings. When false, nullable schemas are treated as optional.

Enables parsing deep object query parameters.

Enables exploring readonly schemas in OpenAPI specifications.

Enables respecting forward compatible enums in OpenAPI specifications.

Enables using the bytes type for binary responses. Defaults to file stream.

The default encoding of form parameters. Options: form, json.

Configure what additionalProperties should default to when not explicitly defined on a schema.

If true, convert strings with format date to strings. If false, convert to dates.

If true, preserve oneOf structures with a single schema. If false, unwrap them.

Endpoints to include in the generated SDK (e.g., “POST /users”).

Controls the maximum depth for which optional properties will have examples generated. A depth of 0 means no optional properties will have examples.

Controls the maximum depth for which optional properties will have examples generated in responses.

Controls whether enums are converted to literal types during code generation. When set to false, enums are preserved as enums rather than being converted to literal types. This is useful when you want to maintain the original enum structure from your OpenAPI specification.

Controls the naming convention for autogenerated request names. When enabled, places the verb before the noun in request names (e.g., UsersListRequest becomes ListUsersRequest), following more idiomatic naming patterns.

Disabled by default to maintain backwards compatibility.

Inlines type aliases to simplify your generated SDK. When enabled, reduces unnecessary type definitions by replacing simple aliases with their underlying types directly. Useful for OpenAPI specs with many primitive or simple type aliases.

Set to true to inline all aliases, or use an object with an except array to preserve specific type aliases:

1
settings:
2
  # Inline all aliases
3
  resolve-aliases: true
4
5
  # Or preserve specific aliases
6
  resolve-aliases:
7
    except:
8
      - UserId
9
      - OrganizationId

When enabled, groups servers by host into unified environments, enabling APIs with multiple protocols (REST, WebSocket, etc.) to share environment configuration. Environment URL IDs use the server name, with path or protocol suffixes added only when needed to resolve collisions.