When would you use a Next.js route handler instead of calling the backend API directly from the browser?

Use Next.js route handlers as an API boundary

Explains route handlers as a frontend server boundary for cookies, API adaptation, auth, and backend calls.

1Say itAnswer out loud first

2CompareCompare with Core answer

3RefineRefine with Stronger and Advanced

TL;DR

I would use a route handler when the frontend server needs to protect tokens, read secure cookies, adapt backend errors, aggregate a page-specific response, or hide backend topology from the browser. The browser calls the route handler, and the route handler calls the ASP.NET API with the right credentials. The backend API still owns domain rules, authorization, validation, and data integrity.

Full answer below

Practice focus

Route handlers, BFF pattern, cookies, token handling, backend API calls, error adaptation, and boundary ownership.

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 question matters
Route handlers are useful, but they can become a confusing second backend if the boundary is unclear. This drill tests practical ownership.
I would use a route handler when the frontend server needs to protect tokens, read secure cookies, adapt backend errors, aggregate a page-specific response, or hide backend topology from the browser. The browser calls the route handler, and the route handler calls the ASP.NET API with the right credentials. The backend API still owns domain rules, authorization, validation, and data integrity.
Checkpoint
Stronger answer
Optional upgrade with examples, trade-offs, and sharper phrasing.
I would keep route handlers thin. They can translate transport concerns and frontend-specific response shapes, but they should not duplicate business logic. If mobile apps, partner clients, or other frontends need the same behavior, it belongs in the backend API. Route handlers also need timeouts, safe error mapping, body size limits, and clear cache behavior, especially when responses are user-specific.
Finish
Advanced answer
Optional deeper angle for production judgment and nuance.
In production I would trace the full path: browser to Next.js route handler to ASP.NET API to database or dependency. Correlation ids and status mapping help support debug failures. Auth is a common risk: tokens should not be exposed to browser JavaScript unnecessarily, and route handlers should not create a privilege escalation path. I would also document which routes are UI-only adapters and which backend endpoints remain the canonical contract.

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

Putting domain authorization only in the route handler.
Duplicating backend business logic in frontend server code.
Caching user-specific route responses as public data.
Hiding backend errors so debugging becomes impossible.

Red flagsCandidateRed flagsSignals that an interviewer may treat as risky.Open details

Details

Cannot explain why a route handler is needed.
Browser tokens are exposed unnecessarily.
Route handler and API disagree about validation or permissions.
No tracing across frontend server and backend API.

Follow-up prompts

Quick interviewer prompts inside this drill.

Follow-up questionsCandidateFollow-up questionsLikely next questions after the main answer.Open details

Details

Treat these as the next interviewer turn. Answer one out loud, then save the gap in your practice notes.

What logic belongs in the route handler?
How would cookies and tokens flow?
When should the browser call the API directly?

Continue the section

Next in Frontend Foundations: Next.js Caching

Step 16 of 30

Caching, revalidation, and dynamic data in Next.js

Opening drill

When would you use a Next.js route handler instead of calling the backend API directly from the browser?

Practice focus

Answer path

Why this question matters

Review signals

Follow-up prompts

Continue the section

When would you use a Next.js route handler instead of calling the backend API directly from the browser?

Practice focus

Answer path

Why this question matters

Review signals

Follow-up prompts

Continue the section