zod

To validate API payloads in TypeScript, create a Zod schema defining expected data structures and parse incoming requests. This enforces type safety, ensuring runtime validation matches static types to prevent brittle API boundaries and runtime failures.

The best way to handle Zod validation errors is using safeParse instead of parse. safeParse returns a structured result object containing success status and error details, allowing you to gracefully manage invalid input without throwing unhandled runtime exceptions.

Derive TypeScript types from Zod schemas using the built-in type inference utility. This automatically generates static types matching your runtime validation rules, ensuring your TypeScript interfaces stay synchronized with your actual validation logic without manual duplication.

Use discriminated unions in Zod for form validation when handling inputs with multiple distinct shapes, such as different user roles or payment methods. They allow safe schema composition and ensure TypeScript correctly narrows types based on specific discriminant fields.

Yes, you can transform input data during validation with Zod. By chaining transformation methods within your schema definitions, Zod allows you to sanitize, format, or convert incoming data while simultaneously ensuring it meets your type safety requirements.