How to use Mock Pagination Response
- Choose the style, total item count and page size.
- Select first/middle/last or a specific page.
- Generate and use each page to test list, scroll and "load more" states.
Mock Pagination Response features
- Page, offset, cursor, keyset and Link-header pagination styles
- First, middle and last pages in one run, or any specific page
- Sequential item ids across pages and decodable base64url cursors
- Links, hasNext/hasPrev flags, totals and X-Total-Count header
- Custom item fields and resource name; seedable
Mock Pagination Response example
Second page of three
Input:
Style: page, total: 25, page size: 10, page: 2Output:
{ "data": [ { "id": 11, … }, …, { "id": 20, … } ], "meta": { "page": 2, "pageSize": 10, "total": 25, "totalPages": 3, "hasPrev": true, "hasNext": true }, "links": { "prev": "…?page=1&pageSize=10", "next": "…?page=3&pageSize=10" } }Frequently asked questions about Mock Pagination Response
Which pagination styles are supported?
Page-based (page/pageSize/totalPages), offset/limit, cursor (pageInfo with opaque base64url cursors), keyset (after_id) and GitHub-style Link headers.
Why first, middle and last pages?
They exercise the three states a client must handle: no previous link, both links, and a partially filled final page with no next link. Generate a specific page when you need another one.
Are the cursors decodable?
Yes. Cursors are base64url-encoded JSON such as {"id":10,"dir":"next"} so you can inspect and craft them in tests.
How are item ids assigned?
Sequentially across pages (page 2 of size 10 starts at id 11), so ordering and de-duplication logic can be verified.