Where does a pagination API live in Next.js?

In the App Router it goes in the GET Route Handler at app/api/.../route.ts. It reads the request query string (?page=N) and returns that page's data as JSON.

What should a pagination response include?

For this problem, the current page, the total number of pages, the total count, and this page's items. The metadata lets the caller navigate between pages.

How do I verify pagination behavior?

Send a normal ?page=N request and check that the page's items and the current page, total page count, and total are all correct, and that a request with no page responds as page 1.

Product List Pagination API

Your task

Build an API that hands out the product list 10 per page instead of all at once. When the caller asks for a given page, return that page's 10 products together with the page info. If no page is given, treat it as 1. Complete the GET handler in app/api/products/route.ts. Note: the caller asks with ?page=N. The response JSON carries page (current page), totalPages (total number of pages), total (total number of products), and items (this page's products).

Ground rules

•Operate on the server-side in-memory catalog (PRODUCTS).
•The page size is fixed at PAGE_SIZE (10).
•Page numbers count from 1 (1-based).

Not required

•Database or external API queries, caching.
•Sorting, search, filtering, cursor pagination.

▶About this challenge

Complete a Next.js GET Route Handler that hands out a product catalog 10 items per page instead of all at once. It reads a ?page=N request, returns that page's items along with the current page, the total page count, the total count, and this page's items as JSON, and covers the default behavior of treating a missing page as page 1.

Pagination serves a large list in page-sized chunks instead of sending everything in one response. The response usually carries not just the current page but also metadata like the total count and total number of pages, so the caller can move to the next or previous page. This problem serves a page of items along with the current page, total page count, and total in the response, plus the default of treating a missing page as page 1, and verifies that a normal ?page=N request returns the right items and metadata.

Where does a pagination API live in Next.js?: In the App Router it goes in the GET Route Handler at app/api/.../route.ts. It reads the request query string (?page=N) and returns that page's data as JSON.
What should a pagination response include?: For this problem, the current page, the total number of pages, the total count, and this page's items. The metadata lets the caller navigate between pages.
How do I verify pagination behavior?: Send a normal ?page=N request and check that the page's items and the current page, total page count, and total are all correct, and that a request with no page responds as page 1.

Product List Pagination API

Your task

Ground rules

•Operate on the server-side in-memory catalog (PRODUCTS).
•The page size is fixed at PAGE_SIZE (10).
•Page numbers count from 1 (1-based).

Not required

•Database or external API queries, caching.
•Sorting, search, filtering, cursor pagination.

▶About this challenge

Where does a pagination API live in Next.js?: In the App Router it goes in the GET Route Handler at app/api/.../route.ts. It reads the request query string (?page=N) and returns that page's data as JSON.
What should a pagination response include?: For this problem, the current page, the total number of pages, the total count, and this page's items. The metadata lets the caller navigate between pages.
How do I verify pagination behavior?: Send a normal ?page=N request and check that the page's items and the current page, total page count, and total are all correct, and that a request with no page responds as page 1.