Skip to content
Novus Examples
json346 B

API Response — Users Page 2 (JSON)

Page 2 (the final page) of a paginated JSON API response. Paired with page 1 for testing pagination, `hasMore` handling, and list merging.

API testingConversion testing
Preview — first 21 linesjson
{
  "page": 2,
  "pageSize": 2,
  "total": 5,
  "hasMore": true,
  "items": [
    {
      "id": 4,
      "name": "Katherine Johnson",
      "email": "katherine.johnson@example.com",
      "role": "admin"
    },
    {
      "id": 5,
      "name": "Edsger Dijkstra",
      "email": "edsger.dijkstra@example.com",
      "role": "member"
    }
  ]
}

Specifications

Format
JSON
Kind
paginated response
Page
2
Items
2
Total
5

What is a .json file?

JSON (JavaScript Object Notation) is a lightweight, text-based data-interchange format representing objects, arrays, strings, numbers, booleans, and null. It is language-independent, human-readable, and the dominant format for web APIs and configuration. It requires a single well-formed root value.

How to use this file

Use an example JSON file to test parsers and serializers, schema validation, Unicode and number-precision handling, and API request or response processing.

How to use this file for testing

“API Response — Users Page 2 (JSON)” is a deterministic Novus Examples fixture for API testing, Conversion testing. OpenAPI/Swagger specs, GraphQL SDL, JSON Schema, paginated and problem+json error payloads, and webhook samples — for testing API clients, mock servers, contract tests, and schema validators.

Documented properties for this file: JSON. Compare results against paired or grouped companions on this page when present (clean↔damaged, searchable↔scanned, or format twins) so scores stay reproducible across runs.

Download the file once, keep the path stable in CI or local scripts, and treat the spec table as the contract: dimensions, seeds, field lists, and roles are intentional. Corrupt or invalid samples are labelled as such — expect parsers to fail loudly rather than silently accept them.

Data fixtures document their exact quirks — delimiters, encodings, null handling, schema, and row counts — in the spec table. Point your parser or importer at the file and assert it handles the documented edge cases; clean and deliberately-messy siblings make before/after diffs straightforward.

Code examples

import json

with open("users-page-2.json") as f:
    data = json.load(f)
print(type(data), len(data))

Related files

Generated by generation/data_dev_fixtures.py. Free for any use, no attribution required — license.