Skip to content
Novus Examples
json574 B

Sample JWT — Decoded (JSON)

The decoded header and payload of the sample JWT as JSON, alongside the public signing secret and algorithm — the ground truth for checking a JWT decoder's output.

Preview — first 19 linesjson
{
  "header": {
    "alg": "HS256",
    "typ": "JWT"
  },
  "payload": {
    "sub": "sample-user-01",
    "name": "Example User",
    "role": "demo",
    "iss": "novus-examples",
    "iat": 1767225600,
    "exp": 1798761600,
    "note": "SAMPLE TOKEN \u2014 signed with a public example secret. Not for production."
  },
  "signatureAlgorithm": "HS256",
  "secret": "a-string-secret-at-least-256-bits-long",
  "note": "Sample only. This token is signed with a public secret so it can be verified; it grants nothing and must never be used in production."
}

Specifications

Format
JSON
Contents
decoded JWT header + payload + secret
Label
SAMPLE ONLY

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

“Sample JWT — Decoded (JSON)” is a deterministic Novus Examples fixture for JSON parsing, Editor testing. Flat, deeply nested, JSON Lines, and intentionally invalid JSON for testing parsers and error handling.

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.

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("sample-jwt-decoded.json") as f:
    data = json.load(f)
print(type(data), len(data))

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