Why HTTP method handlers (GET, POST) in NextJS? - Purpose & Use Cases

The Big Idea

Discover how splitting GET and POST logic can save you hours of debugging and confusion!

The Scenario

Imagine building a web app where you manually check the request type to decide what to do for each user action, mixing all logic in one place.

The Problem

This manual approach makes your code messy, hard to read, and easy to break when adding new features or fixing bugs.

The Solution

HTTP method handlers let you neatly separate what happens for GET and POST requests, making your code clear, organized, and easier to maintain.

Before vs After

✗ Before

if (req.method === 'GET') { /* handle GET */ } else if (req.method === 'POST') { /* handle POST */ }

✓ After

export async function GET() { /* handle GET */ }
export async function POST() { /* handle POST */ }

What It Enables

This lets you build web APIs that respond correctly to different user actions with clean, simple code.

Real Life Example

When a user visits a page (GET), you show data; when they submit a form (POST), you save their input separately and clearly.

Key Takeaways

Manual request handling mixes logic and gets messy.

HTTP method handlers separate GET and POST cleanly.

This improves code clarity and maintainability.

Practice

1. In Next.js API routes, how do you define a handler for a GET request?

easy

A. Define a function named handleGetRequest and call it manually.

B. Export an async function named GET from the route file.

C. Use app.get() inside the route file.

D. Export a function named getHandler from the route file.

Solution

1. Step 1: Understand Next.js route handler naming

   Next.js expects exported async functions named after HTTP methods like GET or POST to handle those requests.

2. Step 2: Identify the correct naming convention

   Only exporting an async function named GET will handle GET requests automatically.

3. Final Answer:

   Export an async function named GET from the route file. -> Option B

4. Quick Check:

   GET handler = async function named GET [OK]

Hint: Name the function exactly GET to handle GET requests [OK]

Common Mistakes:

• Using incorrect function names like getHandler
• Trying to call handlers manually
• Using Express.js style app.get() in Next.js route files

2. Which of the following is the correct syntax to define a POST handler in a Next.js route file?

easy

A. export async function POST(request) { /* code */ }

B. export async function post(request) { /* code */ }

C. export function POST(request) { /* code */ }

D. export async function handlePOST(request) { /* code */ }

Solution

1. Step 1: Check function naming and case sensitivity

   Next.js requires the handler function to be named exactly POST in uppercase to handle POST requests.

2. Step 2: Confirm async keyword usage

   Handler functions should be async to handle asynchronous operations like reading request body.

3. Final Answer:

   export async function POST(request) { /* code */ } -> Option A

4. Quick Check:

   POST handler = async function named POST [OK]

Hint: Use uppercase POST and async keyword for POST handlers [OK]

Common Mistakes:

• Using lowercase 'post' instead of uppercase 'POST'
• Omitting async keyword
• Wrong function names like handlePOST

3. Given this Next.js route handler code, what will be the response to a POST request?

export async function POST(request) {
  const data = await request.json();
  return new Response(JSON.stringify({ message: `Hello, ${data.name}!` }), { status: 200 });
}

And the client sends JSON {"name": "Alice"} in the POST body.

medium

A. SyntaxError due to missing await

B. Empty response with status 200

C. {"message":"Hello, Alice!"}

D. Error: request.json() is not a function

Solution

1. Step 1: Understand request.json() usage

   The code uses await request.json() to parse the JSON body sent by the client, which contains {"name": "Alice"}.

2. Step 2: Construct response with personalized message

   The response JSON string includes the message "Hello, Alice!" using the parsed data.name.

3. Final Answer:

   {"message":"Hello, Alice!"} -> Option C

4. Quick Check:

   POST JSON parsed and response includes name [OK]

Hint: Use await request.json() to read POST JSON body [OK]

Common Mistakes:

• Forgetting to await request.json()
• Returning empty or wrong response
• Misnaming the data property

4. Identify the error in this Next.js route file code for handling GET and POST requests:

export async function GET() {
  return new Response('Hello GET');
}

export function POST(request) {
  const data = request.json();
  return new Response(`Hello ${data.name}`);
}

medium

A. POST handler should be named post in lowercase

B. GET handler should not return Response directly

C. GET handler must accept a request parameter

D. POST handler is missing async keyword and await for request.json()

Solution

1. Step 1: Check POST handler async usage

   The POST handler calls request.json() which returns a promise, so it must be awaited and the function must be async.

2. Step 2: Confirm GET handler and naming

   The GET handler is correctly async and returns a Response; naming and parameters are correct.

3. Final Answer:

   POST handler is missing async keyword and await for request.json() -> Option D

4. Quick Check:

   Async + await needed for request.json() in POST [OK]

Hint: Always use async and await when calling request.json() [OK]

Common Mistakes:

• Not marking POST handler async
• Not awaiting request.json()
• Incorrect handler function names

5. You want to create a Next.js route that responds to both GET and POST requests. The GET returns a JSON list of items, and the POST adds a new item sent in JSON body. Which is the best way to structure your route file?

hard

A. Export async functions named GET and POST; GET returns JSON list; POST reads JSON body and returns updated list.

B. Export a single function handling both GET and POST by checking request.method manually.

C. Use middleware to separate GET and POST logic in different files.

D. Define GET and POST as methods inside a class and export the class.

Solution

1. Step 1: Understand Next.js route handler pattern

   Next.js expects separate exported async functions named after HTTP methods like GET and POST to handle those requests cleanly.

2. Step 2: Structure handlers for each method

   Define GET to return the JSON list and POST to read the JSON body and return the updated list, each in their own async function.

3. Final Answer:

   Export async functions named GET and POST; GET returns JSON list; POST reads JSON body and returns updated list. -> Option A

4. Quick Check:

   Separate GET and POST async functions = clean Next.js pattern [OK]

Hint: Use separate async GET and POST functions for clarity [OK]

Common Mistakes:

• Combining GET and POST in one function
• Using classes or middleware unnecessarily
• Not returning proper JSON responses