What is the difference between model binding and validation in an ASP.NET Core API?

Model binding vs validation in ASP.NET Core

Compare request binding and validation responsibilities in ASP.NET Core APIs.

1Say itAnswer out loud first

2CompareCompare with Core answer

3RefineRefine with Stronger and Advanced

TL;DR

Model binding reads route, query, header, form, or body values and converts them into parameters or a request DTO. Validation runs after or alongside that conversion and checks rules such as required values, ranges, lengths, and allowed combinations. A value can bind successfully and still be invalid: pageSize=5000 is a valid integer but may violate the API's maximum page size.

Full answer below

Practice focus

input conversion, request DTOs, contract validation, business rules, and error consistency

Answer first

Answer path

Core answer first, then checkpoints toward a stronger answer.

Start
Core answer
Start here. This is the direct spoken answer to practice first.
Why this matters
Binding answers whether request data can be converted into the endpoint's .NET input shape. Validation answers whether that successfully bound input is allowed for this contract and operation.
Model binding reads route, query, header, form, or body values and converts them into parameters or a request DTO. Validation runs after or alongside that conversion and checks rules such as required values, ranges, lengths, and allowed combinations. A value can bind successfully and still be invalid: pageSize=5000 is a valid integer but may violate the API's maximum page size.
Checkpoint
Stronger answer
Optional upgrade with examples, trade-offs, and sharper phrasing.
I separate malformed input from validly shaped input that violates the request contract. Invalid JSON or an unparseable route value is a binding failure. A missing name, negative quantity, or invalid date range is validation. Request DTO validation protects the transport contract, application services enforce use-case rules such as account state, and domain objects protect invariants shared by every entry point. That keeps controllers thin without pushing HTTP parsing concerns into the domain.

Review signals

Use these to catch weak phrasing, shallow reasoning, and risky claims.

Common mistakesCandidateCommon mistakesMistakes that weaken the answer or signal shallow understanding.Open details

Details

Assuming binding means valid input
Putting all business rules in DTO attributes
Returning inconsistent validation errors
Relying on frontend validation only
Binding directly to EF entities

What is the difference between model binding and validation in an ASP.NET Core API?

Practice focus

Answer path

Why this matters

Review signals

Follow-up prompts

Continue practice

Next interviewer turn

Skill areas

Suggest an improvement