litestar-dto

Enforce explicit inbound and outbound payload transformations in Litestar by defining ReadDTO and WriteDTO pairs for your models and attaching them to handlers, controllers, or routers to govern how data enters and leaves your API endpoints.

Exclude or rename fields in a Litestar API payload by applying DTOConfig policies. DTOConfig allows you to explicitly specify fields to exclude, rename fields, set max nested depth, and forbid unknown fields for strict contract stability.

You can apply different DTO configurations at the handler, controller, router, or app layers in Litestar. The framework supports layer-specific dto and return_dto definitions, allowing nested field policies to override or refine broader app-level configurations.

Handle partial updates and controlled mutations in Litestar by using the partial parameter within DTOConfig alongside DTOData. DTOData enables safe create and update operations by providing controlled access to inbound data and nested field paths.

You need a custom AbstractDTO implementation in Litestar when standard DTO factories cannot cover your specific payload transformation requirements. Custom AbstractDTO support allows you to define explicit, complex data shaping logic for your API handlers.

Use separate ReadDTO and WriteDTO configurations in a Litestar backend to protect internal models and enforce contract stability. Explicitly shaping inbound and outbound payloads prevents data overexposure and ensures consistent API transformations across the stack.