
API Problem+JSON — Unprocessable Entity (422)
RFC 7807 SAMPLE problem document for HTTP 422 (Unprocessable Entity) client tests.
- File
- JSON · Api
- Use case
- JSON parsingError handling+1· Conversion set
Search files, editable visual templates, and live browser targets from one registry-backed directory. Filtered query views stay crawlable for links but are deliberately noindex; the stable taxonomy pages below remain the canonical search surfaces.
Page 2 of 18; 24 results per page.

RFC 7807 SAMPLE problem document for HTTP 422 (Unprocessable Entity) client tests.

RFC 7807 SAMPLE problem document for HTTP 415 (Unsupported Media Type) client tests.

Rate-limit header values captured as JSON for middleware testing.

Page 1 of a paginated JSON API response (users), with page metadata and a `hasMore` flag. Paired with page 2 for testing pagination and infinite-scroll logic.

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

Paginated response where total count disagrees with items length — tests inconsistency detection.

Sample INI config file for legacy config parser tests.

Sample TOML application config for TOML parser tests.

JSON application settings for config-merge and validation tests.

A well-formed Atom feed with multiple entries — for testing feed readers and parsers.

The same records as Apache Avro — a compact row-based binary format that embeds its own schema, widely used in Kafka pipelines. For testing Avro decoders and schema evolution.

The compatible Avro record schema for reader/writer compatibility tests. Backward compatible for old records: nullable email is added with a null default.

The baseline Avro record schema for reader/writer compatibility tests. Reference writer schema: id and name are strings.

The breaking Avro record schema for reader/writer compatibility tests. Breaking relative to baseline: id changes to long and tenantId has no default.

AWS credentials file shape with obviously fake keys — for credential scanner and parser tests.

A bank-transaction statement — 60 debits and credits across three accounts (masked numbers) with running balances, categories, and merchants. Synthetic data for testing statement parsers, categorisation, and reconciliation.

The bank transactions as a JSON array — the format twin of the CSV, for import and reconciliation testing.

A BibTeX bibliography with three real citations (Lovelace, Knuth, Shannon) across article, book, and inproceedings types — for testing BibTeX parsers, reference managers, and citation converters.

The records as BSON — the binary-JSON encoding MongoDB stores documents in. For testing BSON decoders and JSON↔BSON conversion.

An intentionally corrupt iCalendar file whose VEVENT is never closed, for testing fatal component-nesting errors without using a large or hostile payload.

A complete iCalendar structure using LF-only line endings, a common recoverable export defect for tolerant parser tests.

A standards-conforming event with a folded content line and UTF-8 text for baseline parser and line-unfolding tests.

A recurrence set with both an exclusion and an explicit addition, useful for catching expansion engines that apply only one modifier.

A weekly five-occurrence series that provides the recurrence baseline before exclusions or additions are applied.
We use Google Analytics and show ads via Adsterra. Non-essential cookies and ad scripts run only after you allow the matching categories. See our cookie policy.