Skip to content
Testaroo
json168 B

API Error: 404 (RFC 9457 problem+json)

A 404 error body in RFC 9457 (problem+json) form, with type, title, status, detail, and instance, for testing structured error handling and problem-detail parsers.

API testingConversion testing
Preview, first 8 linesjson
{
  "type": "https://example.com/errors/not-found",
  "title": "Not Found",
  "status": 404,
  "detail": "No user exists with id 999.",
  "instance": "/v1/users/999"
}

Specifications

Format
application/problem+json
Status
404
Spec
RFC 9457

Testing contract

Expected to pass
Scenario
Exercise API Error: 404 (RFC 9457 problem+json) in its api workflow. A 404 error body in RFC 9457 (problem+json) form, with type, title, status, detail, and instance, for testing structured error handling and problem-detail parsers.
Expected result
top-level keys are type, title, status, detail, instance; selected values: {"type": "https://example.com/errors/not-found", "status": 404}. Declared feature checks: status=404; spec=RFC 9457.

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 Error: 404 (RFC 9457 problem+json)” is a deterministic Testaroo 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: application/problem+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("error-404.json") as f:
    data = json.load(f)
print(type(data), len(data))

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

Related files