Technologies Coding Problems Bookmarks Learning Paths

Technologies Coding Problems Bookmarks Learning Paths

AI-powered interview preparation platform. Practice with curated questions, mock interviews, and personalized learning paths to crack your dream tech interview.

Quick Links

Technologies
Saved Questions
Pricing

Company

About Us
Contact Us

Legal

Privacy Policy
Terms of Use

© 2026 nextRound. All rights reserved.

How does API versioning work in NestJS? | Controllers | NestJS Interview Questions | NextRound.in

Questions

3 of 4

1How do you extract route params, query params, and request body in a NestJS controller?

2What happens when you inject @Res() into a handler — what side effect should you be aware of?

3How does API versioning work in NestJS?

4What is the role of a controller in NestJS?

NestJS

Dependency Injection

Request Lifecycle

Exception Handling

Database and ORM

Authentication and Authorization

03 / 04

How does API versioning work in NestJS?

Difficulty: 5/10

URL versioning, Header versioning, Custom versioning

NestJS supports three versioning strategies: URI (/v1/users), HEADER, and MEDIA_TYPE. Enable it with app.enableVersioning({ type: VersioningType.URI }), then annotate controllers or individual routes with @Version('1').

Three versioning strategies:

1
URI versioning — version appears in the URL path: /v1/users.
2
Header versioning — version is passed in a custom request header.
3
Media type versioning — version is embedded in the Accept header.

Enabling URI versioning

Scenario Questions

0-2 years experience

1We need to add a v2 of an existing GET /users endpoint without breaking existing v1 clients. How would you configure NestJS to expose both versions side by side?
2If a client sends an Accept header of 'application/vnd.myapp.v2+json', what does NestJS do and how do you set that up?

2-5 years experience

1Our service originally used URL versioning (e.g., /v1/orders) but we want to move to header‑based versioning. What code changes are required and what pitfalls might cause routes to stop working?

Follow-up Questions

What are the main trade‑offs between URL‑based and header‑based versioning?
How would you verify that a deprecated version still works after a new release?
Can you walk me through how NestJS resolves the version for an incoming request?

Sharethis question

Share via WhatsApp, X, Facebook, LinkedIn or copy link. Open Graph preview enabled.

2After adding a new v2 controller, calls to /api/v1/users start returning 404. Walk me through how you would debug the routing issue in NestJS.

5-8 years experience

1We expect millions of requests per day and need to support v1, v2, and v3 simultaneously. How would you design the versioning strategy in NestJS to keep runtime overhead low and ensure backward compatibility?
2Suppose you need a custom versioning scheme that reads the API version from a JWT claim. How would you integrate that with NestJS routing and what security considerations arise?
3When using multiple versioning strategies in the same app (URL for public APIs, header for internal ones), how do you avoid conflicts and keep the codebase maintainable?

8+ years experience

1Our monorepo has several teams, each owning different modules, and we need to support legacy v1 clients while rolling out v3. How would you structure the NestJS project and versioning approach to allow independent deployment of versioned modules behind a single gateway?
2Design a 12‑month deprecation plan for v1 that includes type‑safe migrations, automated testing, and minimal downtime across multiple teams. What steps and tooling would you put in place?
3What architectural considerations would you weigh when deciding whether to keep versioning logic inside NestJS versus handling it at an API gateway or reverse proxy?