Skip to content
Testaroo
json235 B

API Problem+JSON: Service Unavailable (503)

RFC 7807 SAMPLE problem document for HTTP 503 (Service Unavailable) client tests.

JSON parsingError handlingSchema / OpenAPI testing
Preview, first 9 linesjson
{
  "type": "https://api.sample.example/problems/service-unavailable",
  "title": "Service Unavailable",
  "status": 503,
  "detail": "Upstream payments SAMPLE down.",
  "instance": "/orders/ORD-SAMPLE-503",
  "sample": true
}

Specifications

Status
503
Rfc
7807
Wave
I
Sample Only
true

Testing contract

Expected to pass
Scenario
Exercise API Problem+JSON: Service Unavailable (503) in its api workflow. RFC 7807 SAMPLE problem document for HTTP 503 (Service Unavailable) client tests.
Expected result
top-level keys are type, title, status, detail, instance, sample; selected values: {"type": "https://api.sample.example/problems/service-unavailable", "status": 503, "sample": true}. Declared feature checks: status=503; rfc=7807.

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 Problem+JSON: Service Unavailable (503)” is a deterministic Testaroo fixture for JSON parsing, Error handling, Schema / OpenAPI testing. Flat, deeply nested, JSON Lines, and intentionally invalid JSON for testing parsers and error handling.

Documented properties for this file: JSON · 235 bytes. 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.

Feed the file to your parser and assert it handles the documented quirks, quoted delimiters, embedded newlines, ragged rows, or invalid syntax; the valid↔invalid distinction is labelled in the title.

Code examples

import json

with open("error-service-unavailable.json") as f:
    data = json.load(f)
print(type(data), len(data))

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

Related files