# CLI options reference

<!-- generated by scripts/build_datamodel_codegen_skill_docs.py; do not edit by hand -->

This file is generated from datamodel-codegen's argparse definitions and shared CLI option metadata.
Regenerate it after CLI option changes:

```bash
uv run python scripts/build_datamodel_codegen_skill_docs.py
```

## Base Options

Input sources, output paths, and schema version handling.

- `--input`: Input file/directory (default: stdin)
- `--input-file-type`: Input file type (default: auto). Use 'jsonschema', 'openapi', 'asyncapi', 'graphql', 'mcp-tools', 'xmlschema', 'protobuf', or 'avro' for schema definitions. Use 'json', 'yaml', or 'csv' for raw sample data to infer a schema automatically. Choices: `auto`, `openapi`, `asyncapi`, `jsonschema`, `mcp-tools`, `xmlschema`, `protobuf`, `avro`, `json`, `yaml`, `dict`, `csv`, `graphql`.
- `--external-ref-mapping`: Map external $ref file paths to Python import packages instead of generating duplicate classes. Accepts one or more mappings after a single flag. Format: "path/to/schema.yaml=mypackage.models". When a $ref points to a mapped file, an import statement is generated instead of a class definition.
- `--output`: Output file (default: stdout)
- `--emit-model-metadata`: Write a separate JSON map from source schema references to generated models and fields.
- `--preset`: Apply an immutable built-in option preset. Preset names include the target Python version so generated syntax is pinned. Choices: `standard-py310-20260619`, `standard-py311-20260619`, `standard-py312-20260619`, `standard-py313-20260619`, `standard-py314-20260619`, `practical-py310-20260619`, `practical-py311-20260619`, `practical-py312-20260619`, `practical-py313-20260619`, `practical-py314-20260619`.
- `--url`: Input file URL. `--input` is ignored when `--url` is used
- `--input-model`: Python import path or file path to a Pydantic v2 model or schema dict (e.g., 'mypackage.module:ClassName', './models.py:ClassName', or 'mypackage.schemas:SCHEMA_DICT'). Can be specified multiple times for related models with inheritance. For dict input, --input-file-type is required. Cannot be used with --input or --url.
- `--input-model-ref-strategy`: Strategy for referenced types in --input-model. 'regenerate-all': Regenerate all types. 'reuse-foreign': Reuse types from different families (Enum, etc.), regenerate same-family. 'reuse-all': Reuse all referenced types via import. If not specified, defaults to regenerate-all behavior. Choices: `regenerate-all`, `reuse-foreign`, `reuse-all`.
- `--encoding`: The encoding of input and output (default: utf-8)
- `--schema-version`: Schema version. Valid values depend on input type: JsonSchema: auto, draft-04, draft-06, draft-07, 2019-09, 2020-12. OpenAPI: auto, 3.0, 3.1, 3.2. AsyncAPI: auto, 2.0, 3.0. XMLSchema: auto, 1.0, 1.1. Protobuf: auto, proto2, proto3, 2023. (default: auto - detected from $schema, openapi/asyncapi field, XML Schema versioning attributes, or Protobuf syntax/edition)
- `--schema-version-mode`: Schema version validation mode. 'lenient': accept all features regardless of version (default). 'strict': warn on features outside declared/detected version. Choices: `lenient`, `strict`.

## Typing Customization

Type annotation, import, and primitive type behavior.

- `--use-pendulum`: use pendulum instead of datetime
- `--use-standard-primitive-types`: Use Python standard library types for string formats (UUID, IPv4Address, etc.) instead of str. Affects dataclass, msgspec, TypedDict output. Pydantic already uses these types by default.
- `--no-use-standard-primitive-types`: Use Python standard library types for string formats (UUID, IPv4Address, etc.) instead of str. Affects dataclass, msgspec, TypedDict output. Pydantic already uses these types by default.
- `--output-datetime-class`: Choose Datetime class between AwareDatetime, NaiveDatetime, PastDatetime, FutureDatetime or datetime. Each output model has its default mapping (for example pydantic: datetime, dataclass: str, ...) Choices: `datetime`, `AwareDatetime`, `NaiveDatetime`, `PastDatetime`, `FutureDatetime`.
- `--output-date-class`: Choose Date class between PastDate, FutureDate or date. (Pydantic v2 only) Each output model has its default mapping. Choices: `date`, `PastDate`, `FutureDate`.
- `--enum-field-as-literal`: Parse enum field as literal. all: all enum field type are Literal. one: field type is Literal when an enum has only one possible value. none: always use Enum class (never convert to Literal) Choices: `all`, `one`, `none`.
- `--enum-field-as-literal-map`: Per-field override for enum/literal generation (JSON or JSON file path). Format: JSON object mapping field names to 'literal' or 'enum'. Example: '{"status": "literal", "priority": "enum"}'. Overrides --enum-field-as-literal for matched fields.
- `--ignore-enum-constraints`: Ignore enum constraints and use the base type (e.g., str, int) instead of generating Enum classes
- `--strict-types`: Use strict types Choices: `str`, `bytes`, `int`, `float`, `bool`.
- `--use-annotated`: Use typing.Annotated for Field(). Also, `--field-constraints` option will be enabled. Will become default for Pydantic v2 in a future version.
- `--no-use-annotated`: Use typing.Annotated for Field(). Also, `--field-constraints` option will be enabled. Will become default for Pydantic v2 in a future version.
- `--use-generic-container-types`: Use generic container types for type hinting (typing.Sequence, typing.Mapping). If `--use-standard-collections` option is set, then import from collections.abc instead of typing
- `--use-non-positive-negative-number-constrained-types`: Use the Non{Positive,Negative}{FloatInt} types instead of the corresponding con* constrained types.
- `--use-decimal-for-multiple-of`: Use condecimal instead of confloat for float/number fields with multipleOf constraint (Pydantic only). Avoids floating-point precision issues in validation.
- `--use-standard-collections`: Use standard collections for type hinting (list, dict). Default: enabled
- `--no-use-standard-collections`: Use standard collections for type hinting (list, dict). Default: enabled
- `--use-object-type`: Use object instead of Any for unspecified JSON Schema object and array values
- `--use-specialized-enum`: Use specialized Enum class (StrEnum, IntEnum). Requires --target-python-version 3.11+
- `--no-use-specialized-enum`: Use specialized Enum class (StrEnum, IntEnum). Requires --target-python-version 3.11+
- `--use-union-operator`: Use | operator for Union type (PEP 604). Default: enabled
- `--no-use-union-operator`: Use | operator for Union type (PEP 604). Default: enabled
- `--use-unique-items-as-set`: define field type as `set` when the field attribute has `uniqueItems`
- `--use-tuple-for-fixed-items`: Generate tuple types for arrays with items array syntax when minItems equals maxItems equals items length
- `--use-closed-typed-dict`: Generate TypedDict with PEP 728 closed=True/extra_items for additionalProperties constraints. Use --no-use-closed-typed-dict for type checkers that don't yet support PEP 728 (e.g., mypy).
- `--no-use-closed-typed-dict`: Generate TypedDict with PEP 728 closed=True/extra_items for additionalProperties constraints. Use --no-use-closed-typed-dict for type checkers that don't yet support PEP 728 (e.g., mypy).
- `--allof-merge-mode`: Mode for field merging in allOf schemas. 'constraints': merge only constraints (minItems, maxItems, pattern, etc.) from parent (default). 'all': merge constraints plus annotations (default, examples) from parent. 'none': do not merge any fields from parent properties. Choices: `constraints`, `all`, `none`.
- `--allof-class-hierarchy`: How to map allOf references to class hierarchies. 'if-no-conflict': only create subclasses when parent class has no conflicting property definition. 'always': always create subclasses. Choices: `if-no-conflict`, `always`.
- `--use-type-alias`: Use TypeAlias instead of root models (experimental)
- `--use-root-model-type-alias`: Use type alias format for RootModel (e.g., Foo = RootModel[Bar]) instead of class inheritance (Pydantic v2 only)
- `--disable-future-imports`: Disable __future__ imports
- `--type-mappings`: Override default type mappings. Format: "type+format=target" (e.g., "string+binary=string" to map binary format to string type) or "format=target" (e.g., "binary=string"). Can be specified multiple times.
- `--type-overrides`: Replace schema model types with custom Python types. Format: JSON object mapping model names to Python import paths. Model-level: '{"CustomType": "my_app.types.MyType"}' replaces all references. Scoped: '{"User.field": "my_app.Type"}' replaces specific field only.

## Field Customization

Field naming, aliases, defaults, and constraints.

- `--extra-fields`: Set the generated models to allow, forbid, or ignore extra fields. Choices: `allow`, `ignore`, `forbid`.
- `--use-schema-description`: Use schema description to populate class docstring
- `--use-title-as-name`: use titles as class names of models
- `--infer-union-variant-names`: Infer inline oneOf/anyOf branch model names from literal discriminator-style fields
- `--field-constraints`: Use field constraints and not con* annotations
- `--set-default-enum-member`: Set enum members as default values for enum field
- `--use-enum-values-in-discriminator`: Use enum member literals in discriminator fields instead of string literals
- `--capitalise-enum-members`: Capitalize field names on enum
- `--capitalize-enum-members`: Capitalize field names on enum
- `--empty-enum-field-name`: Set field name when enum value is empty (default: `_`)
- `--field-extra-keys`: Add extra keys to field parameters
- `--field-extra-keys-without-x-prefix`: Add extra keys with `x-` prefix to field parameters. The extra keys are stripped of the `x-` prefix.
- `--field-include-all-keys`: Add all keys to field parameters
- `--original-field-name-delimiter`: Set delimiter to convert to snake case. This option only can be used with --snake-case-field (default: `_` )
- `--remove-special-field-name-prefix`: Remove field name prefix if it has a special meaning e.g. underscores
- `--snake-case-field`: Change camel-case field name to snake-case
- `--no-snake-case-field`: Change camel-case field name to snake-case
- `--special-field-name-prefix`: Set field name prefix when first character can't be used as Python field name (default: `field`)
- `--use-field-description`: Use schema description to populate field docstring
- `--use-field-description-example`: Use schema example to populate field docstring
- `--use-attribute-docstrings`: Set use_attribute_docstrings=True in Pydantic v2 ConfigDict
- `--use-inline-field-description`: Use schema description to populate field docstring as inline docstring
- `--use-single-line-docstring`: Use single-line docstrings when the content fits on one line
- `--no-alias`: Do not add a field alias. E.g., if --snake-case-field is used along with a base class, which has an alias_generator
- `--use-serialization-alias`: Use serialization_alias instead of alias for field aliasing (Pydantic v2 only). This allows setting values using the Pythonic field name while serializing to the original name.
- `--serialization-aliases`: Serialization alias mapping as inline JSON or a JSON file path for Pydantic v2. Format: {'<schema_field>': '<serialization_alias>'}. Supports hierarchical formats: Flat: {'name': 'fullName'} applies to all occurrences. Scoped: {'User.name': 'fullName'} applies to specific class.
- `--field-type-collision-strategy`: Strategy for handling field name and type name collisions (Pydantic v2 only). 'rename-field': rename field with suffix and add alias (default). 'rename-type': rename type class with suffix to preserve field name. Choices: `rename-field`, `rename-type`.
- `--aliases`: Alias mapping as inline JSON or a JSON file path for renaming fields. Format: {'<schema_field>': '<python_name>'} - the schema field name becomes the Pydantic alias. Supports hierarchical formats: Flat: {'id': 'id_'} applies to all occurrences. Scoped: {'User.name': 'user_name'} applies to specific class. Priority: scoped > flat. Multiple aliases (Pydantic v2 only): {'field': ['alt1', 'alt2']} uses AliasChoices for validation. Example: {'User.name': 'user_name', 'id': 'id_'} generates `id_: ... = Field(alias='id')`.
- `--default-values`: Default value overrides as inline JSON or a JSON file path. Supports hierarchical formats: Flat: {'field': value} applies to all occurrences. Scoped: {'ClassName.field': value} applies to specific class. Priority: scoped > flat. Note: Scoped keys use the generated class name for JSON Schema/OpenAPI. Required fields remain required unless --use-default is also specified. Example: {'User.status': 'active', 'page': 1, 'limit': 10}

## Model Customization

Generated model class and package behavior.

- `--output-model-type`: Output model type (default: pydantic_v2.BaseModel) Choices: `pydantic_v2.BaseModel`, `pydantic_v2.dataclass`, `dataclasses.dataclass`, `typing.TypedDict`, `msgspec.Struct`.
- `--allow-extra-fields` (deprecated): Deprecated: --allow-extra-fields is deprecated. Use --extra-fields=allow instead.
- `--allow-population-by-field-name`: Allow population by field name
- `--no-allow-population-by-field-name`: Allow population by field name
- `--class-name`: Set class name of root model
- `--model-name-map`: Rename generated model classes by schema ref or current generated class name using a JSON object or JSON file.
- `--allow-leading-underscore-class-name`: Allow an explicitly specified root class name to start with an underscore
- `--class-name-prefix`: Prefix to add to generated class names (e.g., 'Api' produces 'ApiUser'). Does not apply to root model when --class-name is specified.
- `--class-name-suffix`: Suffix to add to generated class names (e.g., 'Schema' produces 'UserSchema'). Does not apply to root model when --class-name is specified.
- `--class-name-affix-scope`: Scope for applying --class-name-prefix/--class-name-suffix. 'all': Apply to all classes including enums (default). 'models': Apply only to model classes. 'enums': Apply only to enum classes. Choices: `all`, `models`, `enums`.
- `--collapse-root-models`: Models generated with a root-type field will be merged into the models using that root-type model
- `--no-collapse-root-models`: Models generated with a root-type field will be merged into the models using that root-type model
- `--collapse-root-models-name-strategy`: Strategy for naming when collapsing root models that reference other models. 'child': Keep inner model's name (default). 'parent': Use wrapper's name for inner model. Requires --collapse-root-models to be set. Choices: `child`, `parent`.
- `--collapse-reuse-models`: When used with --reuse-model, collapse duplicate models by replacing references instead of creating empty inheritance subclasses. This eliminates 'class Foo(Bar): pass' patterns
- `--skip-root-model`: Skip generating the model for the root schema element
- `--use-root-model-sequence-interface`: Make non-null sequence-like Pydantic v2 RootModel classes implement collections.abc.Sequence by adding Sequence[T] inheritance and root-delegating __iter__, __getitem__, and __len__ methods
- `--enable-faux-immutability`: Enable faux immutability
- `--keep-model-order`: Keep generated models' order
- `--keyword-only`: Defined models as keyword only (for example dataclass(kw_only=True)).
- `--frozen-dataclasses`: Generate frozen dataclasses (dataclass(frozen=True)). Only applies to dataclass output.
- `--dataclass-arguments`: Custom dataclass arguments as a JSON dictionary, e.g. '{"frozen": true, "kw_only": true}'. Overrides --frozen-dataclasses and similar flags.
- `--reuse-model`: Reuse models on the field when a module has the model with the same content
- `--reuse-scope`: Scope for model reuse deduplication: module (per-file, default) or tree (cross-file with shared module). Only effective when --reuse-model is set. Choices: `module`, `tree`.
- `--target-python-version`: target python version Choices: `3.10`, `3.11`, `3.12`, `3.13`, `3.14`.
- `--target-pydantic-version`: Target Pydantic version for generated code. '2': Pydantic 2.0+ compatible (default, uses populate_by_name). '2.11': Pydantic 2.11+ (uses validate_by_name). '2.12': Pydantic 2.12+ (supports MISSING sentinel). Choices: `2`, `2.11`, `2.12`.
- `--alias-generator`: Pydantic v2 BaseModel alias generator to use in ConfigDict. Matching generated aliases are omitted from individual Field() calls. Choices: `to_camel`, `to_pascal`, `to_snake`.
- `--use-generic-base-class`: Generate a shared base class with model configuration (e.g., extra='forbid') instead of repeating the configuration in each model. Keeps code DRY.
- `--parent-scoped-naming` (deprecated): Deprecated: --parent-scoped-naming is deprecated. Use --naming-strategy parent-prefixed instead.
- `--naming-strategy`: Strategy for generating unique model names when duplicates occur. 'numbered' (default): Append numeric suffix (Address, Address1, Address2). Simple but names don't indicate context. 'parent-prefixed': Prefix with parent model name using underscore (Company_Address, Company_Employee_Address for nested). Names show hierarchy. 'full-path': Similar to parent-prefixed but joins with CamelCase (CompanyAddress, CompanyEmployeeAddress). More readable for deep nesting. 'primary-first': Keep clean names for primary definitions (in /definitions/ or /components/schemas/), only add suffix to inline/nested duplicates. Choices: `numbered`, `parent-prefixed`, `full-path`, `primary-first`.
- `--duplicate-name-suffix`: JSON mapping of type to suffix for resolving duplicate name conflicts. Example: '{"model": "Schema"}' changes Address1 to AddressSchema. Keys: 'model' (for classes), 'enum' (for enums), 'default' (fallback). When not specified, uses numeric suffix (Address1, Address2).
- `--base-class`: Base Class (default: pydantic.BaseModel)
- `--base-class-map`: Model-specific base class mapping (JSON or JSON file path). Example: '{"MyModel": "custom.BaseA", "OtherModel": "custom.BaseB"}'. Priority: base-class-map > customBasePath (in schema) > base-class.
- `--use-serialize-as-any`: Use pydantic.SerializeAsAny for fields with types that have subtypes (Pydantic v2 only)
- `--use-one-literal-as-default`: Use one literal as default value for one literal field
- `--use-subclass-enum`: Define generic Enum class as subclass with field type when enum has type (int, float, bytes, str)
- `--model-extra-keys`: Add extra keys from schema extensions (x-* fields) to model_config json_schema_extra
- `--model-extra-keys-without-x-prefix`: Add extra keys with `x-` prefix to model_config json_schema_extra. The extra keys are stripped of the `x-` prefix.
- `--force-optional`: Force optional for required fields
- `--strict-nullable`: Treat default field as a non-nullable field
- `--strip-default-none`: Strip default None on fields
- `--use-default`: Use default value even if a field is required
- `--use-default-kwarg`: Use `default=` instead of a positional argument for Fields that have default values.
- `--use-missing-sentinel`: Use pydantic.experimental.missing_sentinel.MISSING for optional fields without defaults (Pydantic v2.12+).
- `--union-mode`: Union mode for only pydantic v2 field Choices: `smart`, `left_to_right`.
- `--use-frozen-field`: Use Field(frozen=True) for readOnly fields (Pydantic v2).
- `--no-use-frozen-field`: Use Field(frozen=True) for readOnly fields (Pydantic v2).
- `--use-default-factory-for-optional-nested-models`: Use default_factory for optional nested model fields instead of None default. E.g., `field: Model | None = Field(default_factory=Model)` instead of `field: Model | None = None`

## Template Customization

Formatting, custom templates, and generated file headers.

- `--disable-appending-item-suffix`: Disable appending `Item` suffix to model name in an array
- `--disable-timestamp`: Disable timestamp on file headers
- `--enable-version-header`: Enable package version on file headers
- `--enable-command-header`: Enable command-line options on file headers for reproducibility
- `--enable-generated-header-marker`: Enable @generated marker on file headers
- `--treat-dot-as-module`: Treat dotted schema names as module paths, creating nested directory structures (e.g., 'foo.bar.Model' becomes 'foo/bar.py'). Use --no-treat-dot-as-module to keep dots in names as underscores for single-file output.
- `--no-treat-dot-as-module`: Treat dotted schema names as module paths, creating nested directory structures (e.g., 'foo.bar.Model' becomes 'foo/bar.py'). Use --no-treat-dot-as-module to keep dots in names as underscores for single-file output.
- `--use-exact-imports`: import exact types instead of modules, for example: "from .foo import Bar" instead of "from . import foo" with "foo.Bar"
- `--custom-file-header`: Custom file header
- `--custom-file-header-path`: Custom file header file path
- `--custom-template-dir`: Custom template directory
- `--extra-template-data`: Extra template data for output models as inline JSON or a JSON file path. For OpenAPI and Jsonschema the keys are the spec path of the object, or the name of the object if you want to apply the template data to multiple objects with the same name. If you are using another input file type (e.g. GraphQL), the key is the name of the object. The value is a dictionary of the template data to add.
- `--validators`: Validators configuration as inline JSON or a JSON file path. Defines field validators for Pydantic v2 models. Keys are model names, values contain validator definitions with field, function, and mode.
- `--generate-schema-validators`: Generate Pydantic v2 model validators for JSON Schema rules that cannot be represented as type hints (experimental).
- `--schema-validator-type`: Select the schema-derived runtime validator backend. 'pydantic-v2' generates Pydantic v2 model validators (experimental). Choices: `pydantic-v2`.
- `--schema-validator-base-class-name`: Set the generated shared Pydantic v2 schema runtime validator base class name.
- `--use-type-checking-imports`: Allow Ruff to move typing-only imports into TYPE_CHECKING blocks. By default this stays enabled, except for multi-module Ruff formatting of modular Pydantic output where referenced models stay imported at runtime. Use --no-use-type-checking-imports to force runtime imports.
- `--no-use-type-checking-imports`: Allow Ruff to move typing-only imports into TYPE_CHECKING blocks. By default this stays enabled, except for multi-module Ruff formatting of modular Pydantic output where referenced models stay imported at runtime. Use --no-use-type-checking-imports to force runtime imports.
- `--use-double-quotes`: Model generated with double quotes. Single quotes or your black config skip_string_normalization value will be used without this option.
- `--wrap-string-literal`: Wrap string literal by using black `experimental-string-processing` option (require black 20.8b0 or later)
- `--additional-imports`: Custom imports for output (delimited list input). For example "datetime.date,datetime.datetime"
- `--class-decorators`: Custom decorators for generated model classes (delimited list input). For example "@dataclass_json(letter_case=LetterCase.CAMEL)". The "@" prefix is optional and will be added automatically if missing.
- `--formatters`: Formatters for output (default: [black, isort]; use builtin for dependency-free formatting) Choices: `builtin`, `black`, `isort`, `ruff-check`, `ruff-format`.
- `--custom-formatters`: List of modules with custom formatter (delimited list input).
- `--custom-formatters-kwargs`: Custom formatter kwargs as inline JSON or a JSON file path.

## OpenAPI-only Options

OpenAPI-specific generation behavior.

- `--openapi-scopes`: Scopes of OpenAPI model generation (default: schemas) Choices: `schemas`, `paths`, `tags`, `parameters`, `webhooks`, `requestbodies`.
- `--use-operation-id-as-name`: use operation id of OpenAPI as class names of models
- `--include-path-parameters`: Include path parameters in generated parameter models in addition to query parameters (Only OpenAPI)
- `--openapi-include-paths`: Include only OpenAPI paths matching fnmatch patterns. Use wildcards: '*' matches any chars, '?' matches single char. Example: '/users/*' '/products'. Requires '--openapi-scopes' to include 'paths'.
- `--openapi-include-info-version`: Emit OpenAPI info.version as OPENAPI_INFO_VERSION in generated models
- `--validation` (deprecated): Deprecated: The `--validation` option is deprecated and will be removed in a future release. Use --field-constraints instead.
- `--read-only-write-only-model-type`: Model generation for readOnly/writeOnly fields: 'request-response' = Request/Response models only (no base model), 'all' = Base + Request + Response models. Choices: `request-response`, `all`.
- `--use-status-code-in-response-name`: Include HTTP status code in response model names (e.g., ResourceGetResponse200, ResourceGetResponseDefault)

## GraphQL-only Options

GraphQL-specific generation behavior.

- `--graphql-no-typename`: Exclude __typename field from generated GraphQL models. Useful when using generated models for GraphQL mutations.

## General Options

General utility, HTTP, checking, and project integration options.

- `--allow-remote-refs`: Allow fetching remote $ref references over HTTP/HTTPS. Currently remote fetching is allowed by default but emits a deprecation warning. Pass --allow-remote-refs to opt in without warning, or --no-allow-remote-refs to block remote fetching. In a future version, remote fetching will be disabled by default.
- `--no-allow-remote-refs`: Allow fetching remote $ref references over HTTP/HTTPS. Currently remote fetching is allowed by default but emits a deprecation warning. Pass --allow-remote-refs to opt in without warning, or --no-allow-remote-refs to block remote fetching. In a future version, remote fetching will be disabled by default.
- `--allow-private-network`: Allow HTTP(S) schema requests to private, loopback, link-local, or otherwise non-public network hosts. By default these targets are blocked to reduce server-side request forgery (SSRF) risk. If a trusted internal schema endpoint is blocked, verify the URL and pass this option; otherwise use a local schema file or public endpoint. Pass --no-allow-private-network to override a configuration file that enables it.
- `--no-allow-private-network`: Allow HTTP(S) schema requests to private, loopback, link-local, or otherwise non-public network hosts. By default these targets are blocked to reduce server-side request forgery (SSRF) risk. If a trusted internal schema endpoint is blocked, verify the URL and pass this option; otherwise use a local schema file or public endpoint. Pass --no-allow-private-network to override a configuration file that enables it.
- `--http-headers`: Set headers in HTTP requests to the remote host. (example: "Authorization: Basic dXNlcjpwYXNz")
- `--http-query-parameters`: Set query parameters in HTTP requests to the remote host. (example: "ref=branch")
- `--http-ignore-tls`: Disable verification of the remote host's TLS certificate
- `--http-timeout`: Timeout in seconds for HTTP requests to remote hosts (default: 30)
- `--http-local-ref-path`: Resolve HTTP(S) JSON Schema $ref URLs from a local directory instead of fetching them. URLs are mapped under the directory by host and path; extensionless refs also try '.json'.
- `--shared-module-name`: Name of the shared module for --reuse-scope=tree (default: "shared"). Use this option if your schema has a file named "shared".
- `--all-exports-scope`: Generate __all__ in __init__.py with re-exports. 'children': export from direct child modules only. 'recursive': export from all descendant modules. Choices: `children`, `recursive`.
- `--all-exports-collision-strategy`: Strategy for name collisions when using --all-exports-scope=recursive. 'error': raise an error (default). 'minimal-prefix': add module prefix only to colliding names. 'full-prefix': add full module path prefix to colliding names. Choices: `error`, `minimal-prefix`, `full-prefix`.
- `--module-split-mode`: Split generated models into separate files. 'single': generate one file per model class. Choices: `single`.
- `--check`: Verify generated files are up-to-date without modifying them. Exits with code 1 if differences found, 0 if up-to-date. Useful for CI to ensure generated code is committed.
- `--debug`: show debug message (require "debug". `$ pip install 'datamodel-code-generator[debug]'`)
- `--disable-warnings`: disable warnings
- `--list-deprecations`: List registered deprecations and scheduled breaking changes, then exit. Choices: `table`, `json`, `markdown`.
- `--list-experimental`: List registered experimental features, then exit. Choices: `table`, `json`, `markdown`.
- `--help` (alias: `-h`): show this help message and exit
- `--no-color`: disable colorized output
- `--output-format`: Format for command output (default: text). Use json for structured output when supported. Choices: `text`, `json`.
- `--output-format-json-schema`: Output JSON Schema for the selected JSON output or JSON configuration format and exit. Choices: `config`, `generate-prompt`, `generation`, `model-metadata`, `structured-output`.
- `--generate-pyproject-config`: Generate pyproject.toml configuration from the provided CLI arguments and exit
- `--generate-cli-command`: Generate CLI command from pyproject.toml configuration and exit
- `--generate-prompt`: Generate a prompt for consulting LLMs about CLI options. Optionally provide your question as an argument. Pipe to CLI tools (e.g., `| claude -p`, `| codex exec`) or copy to clipboard (e.g., `| pbcopy`, `| xclip`) for web LLM chats.
- `--ignore-pyproject`: Ignore pyproject.toml configuration
- `--profile`: Use a named profile from pyproject.toml [tool.datamodel-codegen.profiles.<name>]
- `--watch`: Watch input file(s) for changes and regenerate output automatically
- `--watch-delay`: Debounce delay in seconds for watch mode (default: 0.5)
- `--version`: show version
