API Route Handlers — Complete Guide
API Route Handlers — Complete Guide: free step-by-step lesson with examples, common mistakes, and interview tips — part of Next.js Tutorial on Toolliyo Academy.
On this page
Next.js Tutorial (LearnHub) · Lesson 22 of 100
API Route Handlers
Beginner ✓ → Intermediate → Advanced → Professional
Intermediate · 2 — Building apps · ~14 min read · Module 3: Data & Forms
Introduction
You know the basics now. Here we use API Route Handlers in real LearnHub screens — layouts, data, and APIs. Still plain language, just a bit more depth. Route Handlers are app/api/**/route.ts files that export GET, POST, PUT, DELETE functions. They return Response or NextResponse JSON for clients outside your React pages. Mobile apps, webhooks, and partner integrations need JSON endpoints. LearnHub might expose GET /api/courses for a native app while the website uses Server Components.
Data and forms power course lists, enrollments, and progress. Learn these patterns slowly — test in a small page first.
When will you use this?
Reach for data fetching and Server Actions when pages need database content or form submissions.
- Enrollments, quiz scores, and course progress load from the server — often with Server Actions.
- Forms that enroll a student in a course use Server Actions instead of a separate REST call.
Real-world: ShopNest storefront
The E-commerce team building ShopNest storefront uses API Route Handlers to expose JSON endpoints for mobile apps or webhooks. customers and admins never see the TypeScript files — they just get a fast, reliable product pages, cart, and checkout flow.
Production-style code
// app/api/courses/route.ts
import { NextResponse } from 'next/server';
export async function GET() {
const courses = [
{ id: '1', title: 'Next.js Fundamentals', lessons: 24 }
];
return NextResponse.json(courses);
}
What happens in production: In ShopNest storefront, getting API Route Handlers right means customers and admins trust the product pages, cart, and checkout flow every day.
Lesson example (start here)
Copy this smaller example first. Once it works, compare it with the real-world code above.
// app/api/courses/route.ts
import { NextResponse } from 'next/server';
const courses = [
{ id: '1', title: 'Next.js Fundamentals', lessons: 24 },
{ id: '2', title: 'TypeScript Essentials', lessons: 18 }
];
export async function GET() {
return NextResponse.json(courses);
}
export async function POST(request: Request) {
const body = await request.json();
return NextResponse.json({ created: body }, { status: 201 });
}
Line-by-line walkthrough
| Code | What it means |
|---|---|
// app/api/courses/route.ts | Comment — notes for humans; the compiler ignores it. |
import { NextResponse } from 'next/server'; | Imports a module so you can use its exports in this file. |
const courses = [ | Part of the API Route Handlers example — read it together with the lines before and after. |
{ id: '1', title: 'Next.js Fundamentals', lessons: 24 }, | Part of the API Route Handlers example — read it together with the lines before and after. |
{ id: '2', title: 'TypeScript Essentials', lessons: 18 } | Part of the API Route Handlers example — read it together with the lines before and after. |
]; | Part of the API Route Handlers example — read it together with the lines before and after. |
export async function GET() { | Exported async function — often a Server Action or API handler. |
return NextResponse.json(courses); | Next.js helpers for Route Handlers — read request and return JSON or redirects. |
} | Closes a block started by { above. |
export async function POST(request: Request) { | Exported async function — often a Server Action or API handler. |
const body = await request.json(); | Part of the API Route Handlers example — read it together with the lines before and after. |
return NextResponse.json({ created: body }, { status: 201 }); | Next.js helpers for Route Handlers — read request and return JSON or redirects. |
} | Closes a block started by { above. |
How it works (big picture)
- GET returns JSON array.
- POST reads request.json() for body.
- Status 201 means created.
- Same-origin fetch from Client Components can call these URLs.
Do this on your computer
- Create app/api/courses/route.ts
- Open /api/courses in browser
- POST with curl or Thunder Client
- Add basic error handling for invalid JSON
- Read the real-world section and name which part of LearnHub uses this topic.
- Run the example locally with npm run dev and confirm the same behavior.
- Change one value in the example (route, text, or course id) and predict what will happen before you save.
Experiments — try changing this
- Change a string or route in the example and save — watch the browser update.
- Break the code on purpose (remove a bracket), read the error overlay, then fix it.
- Change the API URL or course id and see how the page data changes.
- Use npm run dev while editing API Route Handlers — the page hot-reloads on save.
Remember
route.ts = API endpoint. Export HTTP method functions. NextResponse.json for JSON bodies.
Common questions
Route Handlers vs Server Actions?
Handlers for external HTTP clients; Actions for your own forms.
How long should I spend on API Route Handlers?
Until you can explain it in your own words and run the example without looking at the answer. Beginners often need 30–60 minutes per new concept; setup lessons may take one afternoon.
What if I get stuck on API Route Handlers?
Re-read the line-by-line walkthrough, check the terminal and browser overlay for errors, and compare your code character-by-character with the example. Search the exact error text — someone else had it too.
Where is API Route Handlers used in real jobs?
See the real-world section above — the same pattern appears in LMS, e-commerce, SaaS, and dashboards. Interviewers ask you to explain it using one concrete example.