add-api-route

You can scaffold a Next.js API route to proxy backend requests by generating files at src/pages/api/ and integrating with a central apiHelper that manages authentication, error handling, and cache headers. This pattern securely exposes backend services to your frontend.

Aggregating data from multiple backend endpoints in a Next.js API route reduces frontend complexity by building a single server-side proxy endpoint. This approach fetches and combines responses securely before returning the aggregated payload to the client application.

Setting up caching headers for Next.js API routes involves configuring the response headers within your route handler. This skill configures cache headers to cache proxy responses for specified durations, such as 60 seconds, improving frontend application performance.

Yes, the API proxy pattern supports dynamic routes in Next.js. It generates files at src/pages/api/${$0}.ts or src/pages/api/${$0}/index.ts, allowing you to create dynamic route segments that securely forward requests to backend services.

Handling errors when proxying requests through a Next.js API route requires a centralized pattern for robust error handling and retries. This skill integrates with an apiHelper to catch upstream backend failures and return consistent error responses to the frontend.

Use a Next.js API route as a server-side proxy when you need to centralize authentication, implement rate limiting, or apply caching headers. This pattern exposes third-party services securely for frontend consumption without exposing raw backend endpoints.