Mock Pagination Response Generator

How to use

1. 1️⃣
   Choose your options above
2. 2️⃣
   Click Generate
3. 3️⃣
   Copy your result

Detailed instructions

1. Set 'Items per Page' to the page size your real API will use, such as 10, 25, or 50.
2. Enter the 'Current Page' number you want to simulate, starting at 1 for the first page.
3. Set 'Total Items' to your expected dataset size, including odd numbers to test partial last pages.
4. Click Generate to produce a complete JSON response with all pagination metadata computed.
5. Copy the output and paste it into your test fixture, MSW handler, or API documentation example.

Use Cases

• •Populating a TanStack Table or AG Grid component before the backend API exists
• •Creating MSW (Mock Service Worker) handler responses for paginated REST endpoints
• •Testing last-page partial-item behavior with 97 total items and 10 per page in Vitest
• •Generating JSON Server fixture files to power local development with realistic pagination
• •Writing accurate, runnable pagination examples in OpenAPI or Postman collection documentation

Tips

• →Test page 1, a middle page, and the exact last page separately — UI bugs often appear only at boundaries.
• →Use a total like 101 with page size 10 to force an 11-page scenario and quickly spot off-by-one errors in your page count display.
• →If your framework uses 0-indexed pages internally, generate with page 1 and adjust the current_page value in your fixture before committing.
• →Pair the generated JSON with MSW's runtime handler so different page parameters return different generated responses without maintaining multiple files.
• →Set total items to 0 to generate an empty-state response and verify your UI shows the correct 'no results' message instead of broken pagination controls.
• →Match your real API's field naming conventions — if your backend uses camelCase (totalPages vs total_pages), do a quick find-and-replace on the output before using it in tests.

FAQ