🔧 AI Nachrichten Major AI platforms go down in unprecedented simultaneous outage(03.09.2026 um 17:34 Uhr)
🔧 AI Nachrichten ChatGPT, Claude, and Grok Down? Users Report Widespread Outages(03.09.2026 um 19:14 Uhr)
🔧 AI Nachrichten OpenAI Launches GPT-6 Astra, Says We May Have Entered the AGI Era(03.09.2026 um 22:08 Uhr)
🔧 AI Nachrichten Claude Comes to CarPlay as Fifth Major AI Chatbot App(05.09.2026 um 05:31 Uhr)
🔧 AI Nachrichten OpenAI’s GPT-6 Astra Is AGI, Says NVIDIA CEO Jensen Huang(07.09.2026 um 06:31 Uhr)
🔧 AI Nachrichten Blame AI companies for Mac mini and Mac Studio shortage(31.08.2026 um 10:32 Uhr)
🔧 AI Nachrichten Major AI platforms go down in unprecedented simultaneous outage(03.09.2026 um 17:34 Uhr)
🔧 AI Nachrichten ChatGPT, Claude, and Grok Down? Users Report Widespread Outages(03.09.2026 um 19:14 Uhr)
🔧 AI Nachrichten OpenAI Launches GPT-6 Astra, Says We May Have Entered the AGI Era(03.09.2026 um 22:08 Uhr)
🔧 AI Nachrichten Claude Comes to CarPlay as Fifth Major AI Chatbot App(05.09.2026 um 05:31 Uhr)
🔧 AI Nachrichten OpenAI’s GPT-6 Astra Is AGI, Says NVIDIA CEO Jensen Huang(07.09.2026 um 06:31 Uhr)
🔧 AI Nachrichten Blame AI companies for Mac mini and Mac Studio shortage(31.08.2026 um 10:32 Uhr)

🔧 Programmierung 🕛 kürzlich 4 Min Lesezeit
0

Standardized Response and Global Error Handling in Next.js API Routes with Prisma and Zod

↗ Quelle (dev.to)
🗣️ Stimme:
📑 Inhaltsübersicht

We'll start with helper functions for responses and error handling, then implement them in a sample route file with multiple handlers.






Objective





  1. Standardize API Responses: Ensure every API response has a consistent format:




CODE
   {
"success": true,
"message": "Operation completed successfully",
"data": []
}








  1. Implement Global Error Handling: Catch and handle errors (validation errors via Zod, general errors) with consistent formatting, ensuring server stability on errors.






Standard Response Format



We’ll start by creating a helper function to structure our responses. This function will accept data, a message, and a status code to standardize responses.



Create a response.ts file in your lib directory:




CODE
// lib/response.ts

import { NextResponse } from "next/server";

type ApiResponse<T> = {
success: boolean;
message: string;
data?: T;
};

// Helper function for successful responses
export function formatResponse<T>(data: T, message = "Operation completed successfully", status = 200) {
return NextResponse.json<ApiResponse<T>>(
{
success: true,
message,
data,
},
{ status }
);
}

// Helper function for error responses
export function formatErrorResponse(message = "An error occurred", status = 500) {
return NextResponse.json<ApiResponse<null>>(
{
success: false,
message,
data: null,
},
{ status }
);
}









Global Error Handler



Next, let’s create a global error handler to catch validation errors (using Zod) and general server errors, providing consistent messaging for each type.



Create error-handler.ts in your lib directory:




CODE
// lib/error-handler.ts

import { ZodError } from "zod";
import { formatErrorResponse } from "./response";

// Handles different error types
export function routeErrorHandler(error: unknown) {
if (error instanceof ZodError) {
// Handling Zod validation errors
const validationErrors = error.errors.map(err => err.message).join(", ");
return formatErrorResponse(validationErrors, 422);
} else if (error instanceof Error) {
// Handling generic errors
return formatErrorResponse(error.message, 500);
} else {
// Handling unknown errors
return formatErrorResponse("An unknown error occurred", 500);
}
}









Example File Structure






CODE
.
├── app
│ └── api
│ └── users
│ └── route.ts
├── lib
│ ├── error-handler.ts
│ └── response.ts
└── ...









Final Route Example



Below is a complete example of a route.ts file with multiple API operations. Each operation uses formatResponse for successful responses and routeErrorHandler for errors, following our standardized approach.






app/api/users/route.ts






CODE
// app/api/users/route.ts

import { z } from "zod";
import { PrismaClient } from "@prisma/client";
import { formatResponse, formatErrorResponse } from "@/lib/response";
import { routeErrorHandler } from "@/lib/error-handler";

const prisma = new PrismaClient();

// Shared validation schema
const userSchema = z.object({
id: z.string().optional(),
name: z.string().min(1, { message: "Name is required" }),
email: z.string().email({ message: "Invalid email format" }),
});

// Insert a new user
export async function POST(req: Request) {
try {
const json = await req.json();
const validatedData = userSchema.omit({ id: true }).parse(json);

const user = await prisma.user.create({ data: validatedData });
return formatResponse(user, "User created successfully", 201);
} catch (error) {
return routeErrorHandler(error);
}
}

// Update an existing user
export async function PUT(req: Request) {
try {
const json = await req.json();
const validatedData = userSchema.parse(json);

const user = await prisma.user.update({
where: { id: validatedData.id },
data: validatedData,
});
return formatResponse(user, "User updated successfully", 200);
} catch (error) {
return routeErrorHandler(error);
}
}

// Delete a user by ID
export async function DELETE(req: Request) {
try {
const { id } = await req.json();
if (!id) {
return formatErrorResponse("User ID is required", 400);
}

await prisma.user.delete({ where: { id } });
return formatResponse(null, "User deleted successfully", 200);
} catch (error) {
return routeErrorHandler(error);
}
}









Explanation





  1. POST Handler (Insert):




    • Validates request data with userSchema and creates a new user.

    • Returns a success response with formatResponse.




  2. PUT Handler (Update):




    • Validates request data, including id, to update the specified user.

    • Uses formatResponse for a standardized success response.




  3. DELETE Handler (Delete):




    • Accepts an id, validates its existence, and deletes the user.

    • Uses formatResponse to indicate successful deletion or formatErrorResponse if the ID is missing.




  4. Error Handling:




    • Each handler wraps operations in a try-catch block, delegating error handling to routeErrorHandler, which processes both Zod validation errors and general errors in a consistent format.



Vollständiger Original-Bericht
Ausführliche Details, Code-Beispiele & Hersteller-Stellungnahme auf dev.to.
↗ Original-Artikel auf dev.to lesen
Wie bewertest du diesen Beitrag?
1 Klick Feedback
Teilen mit Netzwerk & Team:

Community-Analysen & Experten-Meinungen 0

Verfasse deine eigene Analyse, teile Workarounds oder diskutiere diesen Vorfall im Blog.
Noch keine Community-Analyse verfasst. Markiere einen Textabschnitt oder klicke oben auf Eigene Analyse verfassen“!
Community Pulse: Relevanz-Einschätzung
1 Klick Experten-Votum
🔴 Akute Relevanz 0%
🟡 In Evaluierung 0%
🟢 Keine Auswirkung 0%
Spannende Innovation 0%
Verwandte Story-Cluster & Quellen (Vektor-KI)
Port 8095 Engine
3 Quellen
GPT-6 Astra Release Today? OpenAI’s Next Major AI Model Is Almost Here
1 Quelle
Apple accuses OpenAI of destroying evidence as trade-secrets fight intensifies
1 Quelle
Major AI platforms go down in unprecedented simultaneous outage
Ähnliche Beiträge
🔍 Verwandte News

Auch interessante Nachrichten Standardized Response and Global Error Handling in Next.js API Routes with Prisma and Zod

Thematisch verwandte Begriffe: Standardized, Response, Global, Error · 6 Treffer

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...