OAuth Token Response — SAMPLE
SAMPLE OAuth 2.0 token endpoint JSON with access, refresh, and id_token fields.
{
"access_token": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiJ1c2VyLXNhbXBsZS0wMDEiLCJpc3MiOiJodHRwczovL2F1dGguc2FtcGxlLmV4YW1wbGUvIiwiYXVkIjoibm92dXMtYXBpLXNhbXBsZSIsImlhdCI6MTc2NzIyNTYwMCwiZXhwIjoxNzY3MzEyMDAwLCJuYW1lIjoiU2FtIFJpdmVyYSBTQU1QTEUiLCJ0b2tlbl91c2UiOiJhY2Nlc3MifQ.ZLtK1nKq1uGV11dmI3ngG-6Cvs2x7H_ruDEYu2klL6w",
"token_type": "Bearer",
"expires_in": 3600,
"refresh_token": "novus-sample-refresh-token-wave-g-not-real",
"scope": "openid profile email",
"id_token": "eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCIsImtpZCI6Im5vdnVzLXdhdmUtZy1yc2EifQ.eyJzdWIiOiJ1c2VyLXNhbXBsZS0wMDEiLCJpc3MiOiJodHRwczovL2F1dGguc2FtcGxlLmV4YW1wbGUvIiwiYXVkIjoibm92dXMtYXBpLXNhbXBsZSIsImlhdCI6MTc2NzIyNTYwMCwiZXhwIjoxNzY3MzEyMDAwLCJuYW1lIjoiU2FtIFJpdmVyYSBTQU1QTEUiLCJub25jZSI6InNhbXBsZS1ub25jZS0wMDEifQ.cK4MPKdwnzw3BYaczZpa-rPb5mhYDncLqay-CoVRplDRAq9hupmwIOGnXf38Z_UFZ6cxsjopUYXUdzh_NN_zT6zgrCRySoch5veg6YfsrL8Ev2yUvaVjbvuSeBy7MBmmJAyl5mU4-fwnNjsMtt6FW3ZUP6qI6fUFE1wLgRscsrhTqRv1u07NObYRp9fsa1Xwrr1cc92Kd3UzVE04QYOZ5usT0ExZME33XR4oaPYnCI1Q_At_lqVJD5Ij9ZZ_2ezKhkkjx3HzliaZ31HvT7CNd-m8jOa25JrpxXt5DNdcQXEwrH1CV4asm2bwvYvLBiNMHjnGeggY3rEMRXjV9WNNdQ"
}
Specifications
- Token Type
- Bearer
- Has Id Token
- true
- Sample Only
- true
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
“OAuth Token Response — SAMPLE” is a deterministic Novus Examples fixture for JWT / JWKS testing, API testing. Unsigned and SAMPLE-signed JWT variants plus JWKS documents — published sample material only, for auth parser tests.
Documented properties for this file: JSON · 1,154 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.
This is published, SAMPLE-only security material — never a real secret. Point certificate, key, or token parsers at it, test PEM/DER decoding and PKCS handling, and confirm your tooling reads the documented fields; any sample password is printed on this page.
These JSON fixtures are synthetic SAMPLE auth or tool-call shapes for harnesses — never production secrets or live tokens. Validate schema fields and alg variants against the documented role.
Code examples
import json
with open("token-response.json") as f:
data = json.load(f)
print(type(data), len(data))Related files
- jsonOAuth Device Code Response — SAMPLESAMPLE OAuth device-authorization response for device-flow client tests.
- jsonOAuth Token Error — SAMPLESAMPLE OAuth error JSON for token-endpoint failure handling.
- jsonOAuth Token Introspection — SAMPLESAMPLE RFC 7662-style token introspection response for auth middleware tests.
- jsonOpenID Provider Configuration — SAMPLESAMPLE OpenID Connect discovery document for OIDC client and metadata parsers.
- jsonOAuth Error — Insufficient ScopeOAuth 2.0 SAMPLE error JSON (insufficient_scope) for client error-path tests.
- jsonOAuth Error — Invalid ClientOAuth 2.0 SAMPLE error JSON (invalid_client) for client error-path tests.
Generated by generation/security_wave_g.py. Free for any use, no attribution required — license.