transform

You can transform and validate API payloads by defining Zod schemas that reshape input data into typed outputs. Zod pipelines apply transforms, preprocessing, and coercion to adapt incoming API data into the exact shapes your application expects.

The best way to coerce environment variables and set defaults is using Zod schemas with coercion and default transforms. This approach validates raw environment data and converts it into strongly typed values ready for application configuration loading.

Yes, you can pipe multiple Zod schemas together to build composable validation workflows. Piping connects sequential schemas so the validated output of one transform feeds directly as input into the next, enabling complex data pipeline construction.

Zod supports asynchronous transforms via the parseAsync method. This allows your data pipeline to handle promises and execute async validation logic when reshaping data from APIs or other asynchronous input sources.

You preprocess user input forms by applying Zod preprocess transforms before the main validation schema. This reshapes raw form data, such as trimming strings or converting empty fields, into a consistent state prior to strict type validation.

Zod transforms require the output type to be explicitly defined and can make complex schemas harder to infer automatically. You should avoid overly deep pipeline nesting when reshaping complex data structures to maintain TypeScript type inference readability.